| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\
| |
| | |
Push edit contents to history (issue #1749)
|
| | |
|
|/ |
|
|\
| |
| | |
Fix typo in CHANGELOG.md
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
support keyword args in `show-doc`
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Recover from any SystemCallError on failure to read or write history file
|
|/ |
|
|\
| |
| | |
Fix full scan completion in bare pry
|
|/
|
|
| |
It's not loaded in a bare pry session.
|
| |
|
|\
| |
| | |
Avoid YARD RedundantBraces warnings
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Avoid YARD UnknownParam warning
|
|/ / |
|
|/ |
|
| |
|
| |
|
|
|
| |
screen Pry is running in regardless of platform (Windows or UNIX-like).
|
|
|
| |
lame af
|
| |
|
|
|
|
| |
2.5 (#1728)
|
| |
|
| |
|
|
|
|
|
| |
from_hash is recursive, turning Hash values into Pry::Config objects.
fix #1724
|
|
|
|
|
| |
It's no longer a meaningless file, both because it's outdated and
because Github provides with the same info in a more detailed and
interactive way.
|
|
|
|
|
|
|
|
|
|
|
|
| |
thanks to @dannytatom for the original gem-stats rubygems plugin, which
inspired this Pry command.
it returns some general statistics about a rubygem when given a name.
note that rubygems rate limits the requests, and thanks to that this
command can be a "Fail Whale" although the error is handled gracefully.
This commit depends on pull request:
https://github.com/pry/pry/pull/1701
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
spec suite (#1694)
* Add Pry::Platform.known_engines
* Add fixes for rbx-3.86, and cleanup .travis.yml
* Optionally skip a test on specific Ruby engine(s).
And tag specs that currently do not pass on Rubinius.
Travis takes much longer to complete after this change.
Maybe there are switches we can pass to speed up Rubinius,
or this will improve on new versions of Rubinius.
|
| |
|
|
|
|
| |
instead (as you would with helper functions from BaseHelpers and
CommandHelpers)
|
| |
|
| |
|
|
|
| |
Use bundle exec
|
|
|
|
|
|
|
|
| |
* Abort early when searching for a superclass if the target method
has been called through 'super' keyword from a prepended module.
* mv spec/regression spec/integration
* add hanami integration spec
|
|
|
|
| |
from a default (Pry::Config::Default). Eg, this is no longer an error:
[1] pry(main)> Pry.config.method(:exception_whitelist=)
|
|
|
| |
add new JRuby to the Travis matrix.
|
|
|
|
|
|
|
|
| |
The &block we were capturing is not used or passed anywhere. For performance,
we shouldn't capture a Proc that we do not use. Improve documentation of both
methods.
* update CHANGELOG.md
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* add Pry::Testable, and friends.
This commit replaces lib/pry/test/helper.rb by using category modules.
There's now:
* Pry::Testable:
* Pry::Testable::Evalable
* Pry::Testable::Mockable
* Pry::Testable::Utility
* Pry::Testable::PryTester
'include Pry::Testable' includes all of the above.
For the pry test suite it worked out best to include 'Pry::Testable' at the top-level.
In plugins I've written though this hasn't been the case, and I only normally need:
Pry::Testable::Evalable. So it reduces pollution for the third-party cases, which this
code is intended for since it lives within lib/ of the project.
What do you think?
* breaking change: add set_testenv_variables and unset_testenv_variables
* breaking change: add Pry::Testable::Variables, and rename
constant_scope() to temporary_constants().
* breaking change: rename inject_var as insert_variable, and move its
definition to Pry::Testable::Variables.
* include Pry::Testable::Evalable & include Pry::Testable::Variables into
the top-level, but keep the other two modules spec-local.
* document third argument of insert_variable.
* update CHANGELOG.md
* note changelog entry is a breaking change
* update documentation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Platform is a category module that adds utility functions for querying
platform information relating to Pry.
Some methods are moved from BaseHelpers, and for backwards compatibility
included via 'include Pry::Platform'.
module_function is not used by BaseHelpers anymore, in favour of
include/extend being used in its place.
There is also less indentation noise in BaseHelpers module.
With _pry_.h (available on the backup master branch) these methods
exist on a single module that doesn't pollute the command scope, although
for backwards compatibility we still include the functions as top-level
command functions.
|
|\
| |
| | |
Restore #1649 (sort of)
|
| |\
| |/
|/| |
|
| |
| |
| |
| | |
text on a colorised background.
|
|\ \
| | |
| | | |
Update formatting in CHANGELOG.md
|