Multi-line input only processes the first line #9948

Activity

1. Carreau commented on Sep 17, 2016

   

   Carreau

   on Sep 17, 2016

   Member

   More actions

   Hum, that's probably because the event arrive to fast for processing.
   You are basically typing print 44 while IPython in in between two prompt, as "enter" is both new line and execute (depending if the input is "complete" or not).

   if you try tmux send-keys -t 'test' 'for i in range(10):' Enter 'print 44' Enter if should work.

   We need to bind a shortcut that adds a new line without executing, if you are scripting you can use C-o Down to force a newline and Escape Enter to force execution.
2. languitar commented on Sep 17, 2016

   

   languitar

   on Sep 17, 2016

   Author

   More actions

   My expectation would be that the unprocessed characters after the first enter are just queued up and processed once the first execution returns. This is the behavior that existed in previous versions and which I am used to from basically any other command-line based tool. Simply swallowing key presses doesn't sound nice to me.

   👍React with 👍1Reacted by Mark Steward
3. Carreau commented on Sep 17, 2016

   

   Carreau

   on Sep 17, 2016

   Member

   More actions

   I agree, I was just offering a work around. Though because of IPython
   architecture it might not be that easy to fix.

   The --simple-prompt option might fix that as well, but then you will lose
   most of the bells and whistles, syntactic coloration and multiline edit.

   Unfortunately there is a trade-off

   On Sep 17, 2016 05:05, "Johannes Wienke" [email protected] wrote:

   My expectation would be that the unprocessed characters after the first
   enter are just queued up and processed once the first execution returns.
   This is the behavior that existed in previous versions and which I am used
   to from basically any other command-line based tool. Simply swallowing key
   presses doesn't sound nice to me.

   —
   You are receiving this because you commented.
   Reply to this email directly, view it on GitHub
   #9948 (comment),
   or mute the thread
   https://github.com/notifications/unsubscribe-auth/AAUezzQEQC_zTJvWjD7Gy1EOukxLFPiGks5qq9eegaJpZM4J8jia
   .
4. ivanov commented on Mar 2, 2017

   

   ivanov

   on Mar 2, 2017

   Member

   More actions

   This issue may be the same as the one described in #9948. I want to address this by tackling #10364.
5. jonathanslenders commented on Mar 4, 2017

   

   jonathanslenders

   on Mar 4, 2017

   Last edited by jonathanslenders

   Contributor

   More actions

   I guess the problem here is the send-keys command of tmux doesn't send keystrokes using bracketed paste. If you wrap everything in bracketed paste characters, then I think it should work.

   See: https://cirw.in/blog/bracketed-paste
6. groner commented on Feb 20, 2018

   

   groner

   on Feb 20, 2018

   More actions

   I think paste is just one way of demonstrating the problem.

   Using ipython -im MODULE (or ipython -i SCRIPT) the repl can be delayed while the module or script is loaded, making it easy to type in multiple lines without using paste at all.
7. marksteward commented on Sep 9, 2018

   

   marksteward

   on Sep 9, 2018

   More actions

   I hit this all the time just because of ipython's slow startup. I often find myself writing a couple of lines of code in the time it takes to load, and only the first of them is executed. --simple-prompt and rlwrap makes it usable again, but disables all the useful tab completion.