pry--pry/lib/pry/config.rb

class Pry
  # The Pry config.
  # @api public
  class Config < Pry::BasicObject
    include Behavior

    def self.shortcuts
      Convenience::SHORTCUTS
    end
  end
end
config: simplify structure * Replace `require_relative` with `require` The project tries to use the `require` form everywhere where possible, which is the common form * `require` from `pry.rb` Spreaded `require` statements where we require internal classes is confusing * Fixed namespace definition for Config classes https://github.com/rubocop-hq/ruby-style-guide#namespace-definition recommends to use explicit nesting 2018-10-28 17:45:29 +08:00			`class Pry`
prompt: make it possible to set name dynamically Fixes #1738 (Possible to make prompt_name dynamic?) The user-facing API is the following: ```rb Pry.config.prompt_name = Pry.lazy { rand(100) } [1] 80(main)> [2] 87(main)> [3] 30(main)> ``` 2018-10-28 19:02:14 +08:00			`# The Pry config.`
			`# @api public`
config: simplify structure * Replace `require_relative` with `require` The project tries to use the `require` form everywhere where possible, which is the common form * `require` from `pry.rb` Spreaded `require` statements where we require internal classes is confusing * Fixed namespace definition for Config classes https://github.com/rubocop-hq/ruby-style-guide#namespace-definition recommends to use explicit nesting 2018-10-28 17:45:29 +08:00			`class Config < Pry::BasicObject`
			`include Behavior`

			`def self.shortcuts`
			`Convenience::SHORTCUTS`
			`end`
implement Pry global and pry-local configuration. maybe best explained with an example: [1] pry(main)> Pry.config.hi = "hi" => "hi" [2] pry(main)> _pry_.config.hi => "hi" [3] pry(main)> _pry_.config.x = 1 => 1 [4] pry(main)> Pry.config.x => nil [5] pry(main)> 'Pry.config' is an instance of Pry::Config::Default. it defines the initial default configuration values an instance of 'Pry' is going to have. an instance of 'Pry' uses an instance of Pry::Config who relies on Pry.config as a default or fallback for keys it cannot find locally. for example 'Pry.config.color = true' is seen by _all_ pry REPLs who are active but _pry_.config.color = false is seen only by the REPL session being interacted with. a number of "config shortcircuts" are still available, for example it is possible to say `_pry_.input = StringIO.new` or `Pry.input = StringIO.new`. the shortcuts are maintained for the Pry class and instances of the Pry class through Pry::Config.shortcuts. Pry::Config::Convenience adds a method called 'config_shortcuts' which can be used to setup shortcut access to 'some_obj.config.blah' as 'some_obj.blah' a lot of tests still fail, so work in progress. this should help solve #1055. 2013-12-17 18:27:42 +01:00			`end`
added config.rb to repo 2011-05-28 20:43:32 +12:00			`end`