[Top][All Lists]

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

Re: misbehavior in shell window with ksh

From: Stephen Berman
Subject: Re: misbehavior in shell window with ksh
Date: Mon, 01 May 2017 16:41:06 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

On Mon, 01 May 2017 14:31:11 +0300 Eli Zaretskii <address@hidden> wrote:

>> From: Stephen Berman <address@hidden>
>> Cc: Mike Kupfer <address@hidden>,  address@hidden
>> 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

reply via email to

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