-
-
Save banister/c0fc686ef923c8b87715 to your computer and use it in GitHub Desktop.
The result of running `ls --help` in Pry
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[14] (pry) main: 0> ls -h | |
Usage: ls [-m|-M|-p|-pM] [-q|-v] [-c|-i] [Object] | |
ls [-g] [-l] | |
ls shows you which methods, constants and variables are accessible to Pry. By default it shows you the local variables defined in the current shell, and any public methods or instance variables defined on the current object. | |
The colours used are configurable using Pry.config.ls.*_color, and the separator is Pry.config.ls.separator. | |
Pry.config.ls.ceiling is used to hide methods defined higher up in the inheritance chain, this is by default set to [Object, Module, Class] so that methods defined on all Objects are omitted. The -v flag can be used to ignore this setting and show all methods, while the -q can be used to set the ceiling much lower and show only methods defined on the object or its direct class. | |
options: | |
-m, --methods Show public methods defined on the Object (default) | |
-M, --instance-methods Show methods defined in a Module or Class | |
-p, --ppp Show public, protected (in yellow) and private (in green) methods | |
-q, --quiet Show only methods defined on object.singleton_class and object.class | |
-v, --verbose Show methods and constants on all super-classes (ignores Pry.config.ls.ceiling) | |
-g, --globals Show global variables, including those builtin to Ruby (in cyan) | |
-l, --locals Show locals, including those provided by Pry (in red) | |
-c, --constants Show constants, highlighting classes (in blue), and exceptions (in purple) | |
-i, --ivars Show instance variables (in blue) and class variables (in bright blue) | |
-G, --grep Filter output by regular expression | |
-h, --help Show this message. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
line breaks would be super helpful when viewing this on github