[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: misbehavior in shell window with ksh

From: Eli Zaretskii
Subject: Re: misbehavior in shell window with ksh
Date: Wed, 03 May 2017 20:51:47 +0300

> From: Stephen Berman <address@hidden>
> Cc: address@hidden,  address@hidden
> Date: Tue, 02 May 2017 18:55:01 +0200
> #52 0x0000000000553443 in internal_condition_case_1 (address@hidden 
> <read_process_output_call>, arg=50273987, address@hidden, address@hidden 
> <read_process_output_error_handler>)
>     at /home/steve/git/emacs-master/src/eval.c:1348
> #53 0x0000000000588e2f in read_and_dispose_of_process_output (address@hidden, 
> address@hidden "> ", address@hidden, address@hidden) at 
> /home/steve/git/emacs-master/src/process.c:5979
> #54 0x0000000000589095 in read_process_output (address@hidden, 
> address@hidden) at /home/steve/git/emacs-master/src/process.c:5890
> #55 0x0000000000590a0a in wait_reading_process_output (address@hidden, 
> address@hidden, read_kbd=<optimized out>, address@hidden, address@hidden, 
> address@hidden, just_wait_proc=just---Type <return> to continue, or q 
> <return> to quit---
> address@hidden) at /home/steve/git/emacs-master/src/process.c:5589
> #56 0x0000000000421953 in sit_for (address@hidden, address@hidden, 
> address@hidden)
>     at /home/steve/git/emacs-master/src/dispnew.c:5763
> #57 0x00000000004f313e in read_char (commandflag=1, address@hidden, 
> prev_event=0, address@hidden, address@hidden) at 
> /home/steve/git/emacs-master/src/keyboard.c:2722

The above is the interesting part: it shows that the "> " string was
received from the shell subprocess.  And that rings a bell: we have
this window-adjust-process-window-size-function feature, which is new
in Emacs 25.  It sends a TIOCSWINSZ or TIOCSSIZE ioctl to the shell's
pty; perhaps that causes the shell to respond with PS2?  Can you play
with the value of this variable, like set it to a function that
returns nil, so that set-process-window-size is not called, and see if
that helps to avoid the issue?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]