Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

history of multiline entries #571

Closed
juliantaylor opened this Issue · 5 comments

7 participants

@juliantaylor
Collaborator

Repeating entries with multiple lines via the arrow-up key in 0.11 brings up every line separately which makes repeating them quite awkward due to the lack of operate-and-get-next support.
You have to use the %rep magic to get all lines all at once to edit
In 0.10 this was also done with the arrow-up key

Is there a configuration option to restore the old behavior?

0.11:
In [1]: for i in (1,2):
...: print i
...:
2*arrow-up
In [2]: for i in (1,2):

0.10:
In [1]: for i in (1,2):
...: print i
...:
arrow-up
In [2]: for i in (1,2):
print i

@takluyver
Owner

This is one of those things where whichever way it works, someone's always unhappy. The rationale behind using separate lines is that the terminal is a poor multiline editor, so getting a block of lines is just awkward (and the indentation looks off, because we can't put the ...: prefixes before each line). A config option isn't a bad idea, but hopefully it will be less of an issue as more people start using the Qt console.

@earl

+1 for either restoring the old behaviour or at least making this configurable.

@chl
chl commented

The old behaviour was rather useful, at least for the kinds of short snippets that often occur in ad-hoc analytics. Please restore or make it a configuration option.

@zeekay

Also not a fan of this change. Please make this configurable!

@hipertracker

QT? Are you mad? If someone has access to X-Window he can use much better editors (there are a lot of IDEs). The problem is that now, there is nothing for pure terminal editing. That simple multiline history was useful for casual terminal users.

@juliantaylor juliantaylor referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@juliantaylor juliantaylor referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@juliantaylor juliantaylor referenced this issue from a commit in juliantaylor/ipython
@juliantaylor juliantaylor reenable multiline history for terminals
Add configuration variable InteractiveShell.multiline_history.
If it is True cells spanning multiple lines will be saved in history
as a single entry instead of one entry per line, as was the case in
ipython < 0.11.
closes gh-571
30eccbc
@fperez fperez closed this issue from a commit
@fperez fperez Merge branch 'juliantaylor-multiline-history'
Restore multiline history (on by default) as it worked in the 0.10.x
series.  A new configuration variable
InteractiveShell.multiline_history can be set to control this behavior
for users who prefer not to have it on.

When True, cells spanning multiple lines will be saved in history as a
single entry instead of one entry per line

Closes gh-571.
bf4b2a0
@fperez fperez closed this in bf4b2a0
@ellisonbg ellisonbg referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@fperez fperez referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@mattvonrocketstein mattvonrocketstein referenced this issue from a commit in mattvonrocketstein/ipython
@juliantaylor juliantaylor reenable multiline history for terminals
Add configuration variable InteractiveShell.multiline_history.
If it is True cells spanning multiple lines will be saved in history
as a single entry instead of one entry per line, as was the case in
ipython < 0.11.
closes gh-571
dde8bc4
@mattvonrocketstein mattvonrocketstein referenced this issue from a commit in mattvonrocketstein/ipython
@fperez fperez Merge branch 'juliantaylor-multiline-history'
Restore multiline history (on by default) as it worked in the 0.10.x
series.  A new configuration variable
InteractiveShell.multiline_history can be set to control this behavior
for users who prefer not to have it on.

When True, cells spanning multiple lines will be saved in history as a
single entry instead of one entry per line

Closes gh-571.
ff68dd5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.