[IPython-user] New pyreadline breaks autoindent

[Jörgen Stenarson]

Jerry McRae skrev:
> I get the same results in WinXP.  In addition, with pyreadline 1.4.3, 
> the PgUp and PgDn keys no longer work [to move through your output buffer]
Fixed in svn

> 
> Another "bug" is the the ^k "kill-line" command copies into the 
> ClipBoard (bad) in addition to clearing to EOL (good).  I do NOT want my 
> clipboad updated unless I ask for it.  My clipboard monitor records all 
> cut or copy operations.
The reason for this behaviour was I wanted to be able to yank after a 
kill. This was the easiest way to implement that. However I can see
that it is not ideal behaviour so I have started to create a separate
kill-ring, which at this time will only hold a single kill.

So I think this issue is also fixed in svn now (if you update make sure
your pyreadlineconfig binds ctrl-y to yank and not paste if you want to
be able to yank after a kill)

Anyone else have an opinion on how the kill ring should be implemented 
in relation to clipboard?

> With 0.8.x, using pyreadline 1.4.3 (which I don't have installed right now):
> I believe <ESC> key deletes to start of line AND copies to the clipboard.
Now default is delete entire line (copy to kill-ring and not clipboard)

> 
> One other Windows specific bug, but has been around for a while.  If 
> IPython is started using the IPYTHON.EXE, a ^C will totally confuse it.  
> It toggles between the IPython prompt and the CMD prompt, but neither 
> works well after that.  If IPython is started using ipython_script.py, 
> everything works as expected.  (I noticed this back in the 0.6 version, 
> which has working fine for me, but I haven't seen it mentioned on the 
> list before).

I recognize this. If I remember correctly this is an easyinstall related 
problem. It puts an exe file in the script directory, this exe file 
launches a python process that runs ipython. When you do ctrl-c you kill
the python process but not the starter process which is still confusing 
cmd. At least this was my interpretation of the situation about a year 
ago when I last tried to use easyinstall.

/Jörgen