Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upBlock history #22
Block history #22
Comments
|
Block history and block editing is the last thing needed to make me switch from ipython to bpython. Ipython's block editing is not great, but it is better than line-by-line history. It is tedious and ineffective to change a funciton or class by re-adding it line by line. Original Comment By: David Fendrich |
|
Issue #111 was marked as a duplicate of this issue. Original Comment By: Andreas Stührk |
|
I do not like this suggestion. In fact I do not like block history at all, but if we decide to do this we should need a shortcut to go into and out of block mode. Original Comment By: Simon de Vlieger |
|
have a separate keypress for browsing up and down blocks. Original Comment By: Anonymous |
|
What about a separate "block browser" mode? View previous blocks, edit them in an external editor, then plunk one down? Otherwise the thing that makes the most sense to me is a separate key for block history - displaying the entries will be icky (should be entered into the buffer each time), but possible. Along with the new "edit current block" key (ctrl-x by default (yes this isn't a great keybinding)) being able to change the current buffer could be possible. |
|
I'm once again excited about this, it would take some effort but I'm thinking about it now. |
|
Hello, please, are there any news in this regard? |
|
This is really good feature. Sometimes you have typo, sometimes you missed |




eggy has suggested we have block history. I agree it's a good idea, but I just don't know how to do it without it sucking.
I think that what we're going to have to do is allow the user to move up and down within a block, which means things might get pretty complicated. Also would be a good idea to allow inserting a new line inside the block.
If anyone has any ideas how to do this cleanly please post comments here.