mirror of
https://github.com/pry/pry.git
synced 2022-11-09 12:35:05 -05:00
ebccd57013
John "banister" Mair describes the following key features of commands
as classes:
1. It enables people to extend them by either subclassing or
monkeypatching.
2. It enables them to provide their own API, so that for example, the
Pry::Command::Edit class could have class methods for people to
configure it.
Please, note that I didn't touch easter eggs commands. I also prettified
some strings (your source code reading experience should vastly improve!).
Signed-off-by: Kyrylo Silin <kyrylosilin@gmail.com>
31 lines
850 B
Ruby
31 lines
850 B
Ruby
class Pry
|
|
class Command::Cd < Pry::ClassCommand
|
|
match 'cd'
|
|
group 'Context'
|
|
description 'Move into a new context (object or scope).'
|
|
|
|
banner <<-BANNER
|
|
Usage: cd [OPTIONS] [--help]
|
|
|
|
Move into new context (object or scope). As in unix shells use
|
|
`cd ..` to go back, `cd /` to return to Pry top-level and `cd -`
|
|
to toggle between last two scopes).
|
|
Complex syntax (e.g `cd ../@x/y`) also supported.
|
|
|
|
e.g: `cd @x`
|
|
e.g: `cd ..`
|
|
e.g: `cd /`
|
|
e.g: `cd -`
|
|
|
|
https://github.com/pry/pry/wiki/State-navigation#wiki-Changing_scope
|
|
BANNER
|
|
|
|
def process
|
|
state.old_stack ||= []
|
|
stack, state.old_stack = context_from_object_path(arg_string, _pry_, state.old_stack)
|
|
_pry_.binding_stack = stack if stack
|
|
end
|
|
end
|
|
|
|
Pry::Commands.add_command(Pry::Command::Cd)
|
|
end
|