From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, mkupfer@alum.berkeley.edu
Subject: Re: misbehavior in shell window with ksh
Date: Mon, 01 May 2017 16:41:06 +0200 [thread overview]
Message-ID: <87inlkzlkt.fsf@rosalinde> (raw)
In-Reply-To: <837f20ke4g.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 01 May 2017 14:31:11 +0300")
On Mon, 01 May 2017 14:31:11 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: Mike Kupfer <mkupfer@alum.berkeley.edu>, emacs-devel@gnu.org
>> Date: Mon, 01 May 2017 12:59:21 +0200
>>
>> > 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.)
>
> Thanks, can you debug this to see what's causing the problem?
By edebugging shell.el and comint.el I see that after typing `C-x 0' in
the recipe, the function comint-output-filter is invoked with the value
#<process shell> for its argument `proc' and the value "> " for its
argument `string', and the latter value is what is inserted into the
*shell* buffer. I have failed to find out how that argument gets that
value or even how comint-output-filter gets invoked. If anyone has any
advice for how to proceed, I can try it.
Steve Berman
next prev parent reply other threads:[~2017-05-01 14:41 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inlkzlkt.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 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.