all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org, mkupfer@alum.berkeley.edu
Subject: Re: misbehavior in shell window with ksh
Date: Thu, 04 May 2017 17:42:59 +0300	[thread overview]
Message-ID: <8337ckhedo.fsf@gnu.org> (raw)
In-Reply-To: <87k25xawgg.fsf@rosalinde> (message from Stephen Berman on Thu, 04 May 2017 09:54:23 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: mkupfer@alum.berkeley.edu,  emacs-devel@gnu.org
> Date: Thu, 04 May 2017 09:54:23 +0200
> 
> > 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?
> 
> Bingo!  That variable is a user option and when I change its value with
> M-x customize-option to "Do not adjust process window sizes" (i.e. the
> function `ignore') and then execute the recipe, "> " is not inserted.
> When I return to the customization buffer and change the value back to
> the default "Minimum area of any window" (i.e. the function
> `window-adjust-process-window-size-smallest') and then switch back to
> the *shell* buffer, "> " I see that has now been inserted.

Thanks for looking into this.

Can the shell experts among us please tell whether this is an expected
reaction of a shell to window-resizing ioctl?  And why this is only
seen with ksh?  And why in some cases one needs to set EDITOR in the
environment?

IOW, the window-adjust-process-window-size-function is a standard
feature that is turned on by default; if it turns out that it has
annoying unintended consequences in some use cases, we will have to
rethink when we turn it on and off, IMO.



  reply	other threads:[~2017-05-04 14:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 23:12 misbehavior in shell window with ksh Mike Kupfer
2017-05-01  6:49 ` Eli Zaretskii
2017-05-01 10:59   ` Stephen Berman
2017-05-01 11:31     ` Eli Zaretskii
2017-05-01 14:41       ` Stephen Berman
2017-05-01 15:09         ` Eli Zaretskii
2017-05-01 15:52           ` Stephen Berman
2017-05-02  9:03             ` Eli Zaretskii
2017-05-02 12:35               ` Stephen Berman
2017-05-02 16:32                 ` Eli Zaretskii
2017-05-02 16:55                   ` Stephen Berman
2017-05-03 17:51                     ` Eli Zaretskii
2017-05-04  7:54                       ` Stephen Berman
2017-05-04 14:42                         ` Eli Zaretskii [this message]
2017-05-05  3:04                           ` Mike Kupfer
2017-05-05  6:13                             ` Eli Zaretskii
2017-05-06 18:41                               ` Mike Kupfer
2017-05-09 16:36                                 ` Eli Zaretskii
2017-05-01 15:29         ` Mike Kupfer
2017-05-02 13:03           ` Tino Calancha
2017-05-01  7:38 ` Tino Calancha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8337ckhedo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mkupfer@alum.berkeley.edu \
    --cc=stephen.berman@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.