customizable cpaste #103

Closed
ipython opened this Issue May 10, 2010 · 2 comments

Comments

Projects
None yet
2 participants
@ghost
Collaborator

ghost commented May 10, 2010

Original Launchpad bug 237504: https://bugs.launchpad.net/ipython/+bug/237504
Reported by: fdo.perez (Fernando Perez).

Idea requested by Joe Harrington:

How hard would it be (and would you be willing) to add a feature to
cpaste that lets you replace strings on package names? This would let
a user tell cpaste to replace "np" with "N", for example, so that they
could cut-and-paste a doc example into their session and not have it
break if they don't use the "np" abbreviation.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 10, 2010

Collaborator

[ LP comment 1 by: Ville M. Vainio, on 2008-09-13 07:53:18.709133+00:00 ]

I special cased:

%edit pasted_block

so that it saves the new value for pasted_block. Therefore, you can execute "edit pasted_block" in succession to polish your pasted code. This would make this feature request unnecessary (since of course you can do all the search & replace in your editor as you see fit).

(implemented in my trunk-dev)

Collaborator

ghost commented May 10, 2010

[ LP comment 1 by: Ville M. Vainio, on 2008-09-13 07:53:18.709133+00:00 ]

I special cased:

%edit pasted_block

so that it saves the new value for pasted_block. Therefore, you can execute "edit pasted_block" in succession to polish your pasted code. This would make this feature request unnecessary (since of course you can do all the search & replace in your editor as you see fit).

(implemented in my trunk-dev)

@ghost ghost assigned fperez Apr 10, 2011

@fperez

This comment has been minimized.

Show comment
Hide comment
@fperez

fperez Nov 30, 2011

Member

The solution proposed above has already been merged, so this can be closed.

Member

fperez commented Nov 30, 2011

The solution proposed above has already been merged, so this can be closed.

@fperez fperez closed this Nov 30, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment