From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Mike Kupfer <mkupfer@alum.berkeley.edu>
Subject: Re: misbehavior in shell window with ksh
Date: Mon, 01 May 2017 12:59:21 +0200 [thread overview]
Message-ID: <87pofszvue.fsf@rosalinde> (raw)
In-Reply-To: 83o9vdjcl6.fsf@gnu.org
On Mon, 01 May 2017 09:49:41 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Mike Kupfer <mkupfer@alum.berkeley.edu>
>> Date: Sun, 30 Apr 2017 16:12:26 -0700
>>
>> >From emacs -Q, using Emacs master 6fa9cc05, if I do the following steps
>>
>> M-x shell RET
>> ksh RET
>> C-x o RET
>> C-x 0 RET
>>
>> a ">" appears after the shell prompt in the *shell* buffer:
>>
>> alto$ ksh
>> alto$ >
>>
>> If I then press RET, I get
>>
>> alto$ ksh
>> alto$ >
>> : not found [No such file or directory]
>> alto$
>
> I cannot reproduce this, neither with Emacs 25.2 nor with the latest
> master branch.
>
> Does this happen in a -nw session as well, or only in GUI frames?
I can reproduce this with both -Q and -Q -nw in latest master (details
below). I also noticed that (any?) non-self-insertion keyboard events
reproduce the behavior, e.g. `t TAB' adds anoth `>' at the prompt, and
then `C-g' to kill the *Completions* buffer adds another `>', and then
RET returns:
^L^Lt: not found [No such file or directory]
(Then ^L are really control characters.)
In GNU Emacs 26.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.20.10)
of 2017-05-01 built on rosalinde
Repository revision: 6c9ec085e2b36e801c967bc0635671dc1880cb80
Repository revision: edc63bf94f3cd3f52fab86fe7b92a3ec6a19de40
Windowing system distributor 'The X.Org Foundation', version 11.0.11803000
System Description: openSUSE Leap 42.2
Configured using:
'configure --with-xwidgets 'CFLAGS=-Og -g3''
Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND DBUS GSETTINGS NOTIFY
GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS
GTK3 X11 XWIDGETS
Important settings:
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: @im=local
locale-coding-system: utf-8-unix
next prev parent reply other threads:[~2017-05-01 10:59 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pofszvue.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mkupfer@alum.berkeley.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).