From: Phil Sainty <psainty@orcon.net.nz>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31193@debbugs.gnu.org,
bug-gnu-emacs
<bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org>
Subject: bug#31193: 26.1; error in `term-down' after window configuration change
Date: Wed, 18 Apr 2018 16:23:37 +1200 [thread overview]
Message-ID: <77839205bfe30db7b7a50428065d3714@webmail.orcon.net.nz> (raw)
In-Reply-To: <87h8o9tglt.fsf@gmail.com>
On 2018-04-18 14:04, Noam Postavsky wrote:
>> term-emulate-terminal(#<process terminal> "\015\033[K$
>> \015\n\032//home/phil/emacs/26/26.1rc1/usr/local/share/emacs/26.1/lisp\015\n")
>
> Hmm, yeah, it looks like your bash adds a "\r\n" (\015 is \r) after the
> prompt, while mine doesn't. Although, wouldn't that extra \n leave
> your
> cursor one row below the prompt?
In practice the carriage return shunts the cursor back to the start of
the
prompt that I was already at, and then gets 'stuck' there -- no new line
is
created.
Typing RET again triggers the same error (with no change to the buffer),
but as soon as I start typing other keys, functionality is restored.
> I also don't get the \032/<path>\r\n unless I do a 'cd'.
I observe that whenever I execute a shell command (or just enter a blank
line) and then trigger the error, I get this the first time:
term-emulate-terminal(#<process terminal> "\015\033[K$\015\n")
but repeatedly re-triggering the error gives me this every time:
term-emulate-terminal(#<process terminal>
"\015\033[K$\015\n\032/<path>\015\n$")
(until I next enter a command or blank line.)
The <path> matches the directory tracking -- I can affect it with cd.
(but setting default-directory does not affect it).
next prev parent reply other threads:[~2018-04-18 4:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 13:00 bug#31193: 26.1; error in `term-down' after window configuration change Phil Sainty
2018-04-17 13:23 ` Noam Postavsky
2018-04-17 13:49 ` Phil Sainty
2018-04-18 0:07 ` Noam Postavsky
2018-04-18 1:04 ` Phil Sainty
2018-04-18 2:04 ` Noam Postavsky
2018-04-18 4:23 ` Phil Sainty [this message]
2018-04-18 12:15 ` Noam Postavsky
2018-04-18 5:05 ` Phil Sainty
2018-04-18 5:37 ` Phil Sainty
2018-04-18 6:25 ` Eli Zaretskii
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=77839205bfe30db7b7a50428065d3714@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=31193@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
--cc=npostavs@gmail.com \
/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).