From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
Subject: Re: misbehavior in shell window with ksh
Date: Fri, 05 May 2017 09:13:31 +0300 [thread overview]
Message-ID: <83wp9vg7as.fsf@gnu.org> (raw)
In-Reply-To: <914.1493953443@alto> (message from Mike Kupfer on Thu, 04 May 2017 20:04:03 -0700)
> From: Mike Kupfer <mkupfer@alum.berkeley.edu>
> cc: Stephen Berman <stephen.berman@gmx.net>, emacs-devel@gnu.org
> Date: Thu, 04 May 2017 20:04:03 -0700
>
> I'm not a shell expert, but I did spend a little time with strace to see
> what ksh is doing.
OK, thanks for looking into this. AFAIU, the conclusion is that
indeed the offending string comes from the shell as result of Emacs's
telling the shell that its screen size has changed.
So is it enough to conclude that users of shells like this should
customize window-adjust-process-window-size-function to avoid telling
the shell its screen has been resized? Or do we need a more thorough
solution for this problem?
next prev parent reply other threads:[~2017-05-05 6:13 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
2017-05-05 3:04 ` Mike Kupfer
2017-05-05 6:13 ` Eli Zaretskii [this message]
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=83wp9vg7as.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.