new ipython history clear subcommand
#4542
Merged
Conversation
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
thanks @jakobgager for pointing this out in ipython#4528
Sometimes, Ctrl-C just makes sense as an answer, and re-asking the question is just frustrating. This changes makes it possible to break out of the asking loop via Ctrl-C. This is particularly handy for asking questions from the command line, where one expects Ctrl-c to be a sort of "Cancel" operation, and is often functionally equivalent to "no"
| @@ -0,0 +1,4 @@ | |||
| * `ipython history trim`: added `--keep=<N>` as an alias for the more verbose | |||
There was a problem hiding this comment.
These should be double backticks:
``ipython history trim``
etc.
|
Other than that, this looks good to me. |
|
LGTM too. |
|
I agree... OK for me too |
|
Yay, good to merge? |
|
👍 I'm sure I'll find other excuses to mess with bash completion later ;) |
minrk
added a commit
that referenced
this pull request
Nov 22, 2013
new `ipython history clear` subcommand This new subcommand is equivalent to ipython history trim --HistoryTrim.keep=0, which is now supported (and also has a more convenient --keep alias) This command comes with a fix to bash completion of flags for ipython history subcmd also included is a tiny fix for nbconvert completion that was pointed out by @jakobgager in #4528 also included is a change to our utils.io.ask_yes_no function that allows for specifying the behavior of a KeyboardInterrupt.
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
new `ipython history clear` subcommand This new subcommand is equivalent to ipython history trim --HistoryTrim.keep=0, which is now supported (and also has a more convenient --keep alias) This command comes with a fix to bash completion of flags for ipython history subcmd also included is a tiny fix for nbconvert completion that was pointed out by @jakobgager in ipython#4528 also included is a change to our utils.io.ask_yes_no function that allows for specifying the behavior of a KeyboardInterrupt.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This new subcommand is equivalent to
ipython history trim --HistoryTrim.keep=0, which is now supported (and also has a more convenient--keepalias)This command comes with a fix to bash completion of flags for
ipython history subcmdalso included is a tiny fix for nbconvert completion that was pointed out by @jakobgager in #4528
also included is a change to our utils.io.ask_yes_no function that allows for specifying the behavior of a KeyboardInterrupt.