On Fri, Feb 27, 2009 at 7:56 PM, Stephan Peijnik <email address hidden> wrote:
> I am somewhat wondering why "%hist -r" executes the piece of code in its history again, as it shouldn't do that.
It doesn't - it's just that readline is feeding our raw_input
characters that it shouldn't. You should run %hist -r (and %hist
without -r) to get a hint about what's happening.
> Right now I am wondering whether this bug isn't more severe than I initially thought. If %hist executes commands this could cause bad things to
happen (think of a call to os.remove being executed again, after
changing the working directory).
It's certainly a very serious issue - unfortunately it's something we
probably can't easily get rid of, since we are blindly relying on the
hope that we get sensible input from the terminal.
On Fri, Feb 27, 2009 at 7:56 PM, Stephan Peijnik <email address hidden> wrote:
> I am somewhat wondering why "%hist -r" executes the piece of code in its history again, as it shouldn't do that.
It doesn't - it's just that readline is feeding our raw_input
characters that it shouldn't. You should run %hist -r (and %hist
without -r) to get a hint about what's happening.
> Right now I am wondering whether this bug isn't more severe than I initially thought. If %hist executes commands this could cause bad things to
happen (think of a call to os.remove being executed again, after
changing the working directory).
It's certainly a very serious issue - unfortunately it's something we
probably can't easily get rid of, since we are blindly relying on the
hope that we get sensible input from the terminal.
-- tinyurl. com/vainio
Ville M. Vainio
http://