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>
44 lines
1.2 KiB
Ruby
44 lines
1.2 KiB
Ruby
class Pry
|
|
class Command::Exit < Pry::ClassCommand
|
|
match 'exit'
|
|
group 'Navigating Pry'
|
|
description 'Pop the previous binding (does NOT exit program). Aliases: quit'
|
|
|
|
banner <<-BANNER
|
|
Usage: exit [OPTIONS] [--help]
|
|
Aliases: quit
|
|
|
|
It can be useful to exit a context with a user-provided value. For
|
|
instance an exit value can be used to determine program flow.
|
|
|
|
e.g: `exit "pry this"`
|
|
e.g: `exit`
|
|
|
|
https://github.com/pry/pry/wiki/State-navigation#wiki-Exit_with_value
|
|
BANNER
|
|
|
|
command_options(
|
|
:keep_retval => true
|
|
)
|
|
|
|
def process
|
|
if _pry_.binding_stack.one?
|
|
_pry_.run_command "exit-all #{arg_string}"
|
|
else
|
|
# otherwise just pop a binding and return user supplied value
|
|
process_pop_and_return
|
|
end
|
|
end
|
|
|
|
def process_pop_and_return
|
|
popped_object = _pry_.binding_stack.pop.eval('self')
|
|
|
|
# return a user-specified value if given otherwise return the object
|
|
return target.eval(arg_string) unless arg_string.empty?
|
|
popped_object
|
|
end
|
|
end
|
|
|
|
Pry::Commands.add_command(Pry::Command::Exit)
|
|
Pry::Commands.alias_command 'quit', 'exit'
|
|
end
|