From: Eli Zaretskii <eliz@gnu.org>
To: Michael Hoffman <hoffman@cantab.net>
Cc: 11919-done@debbugs.gnu.org, 0wdp3p2xrt@sneakemail.com,
gmane3-hoffman@snkmail.com
Subject: bug#11919: 24.1; term-emulate-term does not process bash's Ctrl-Z signal of directory name when an AnSi message is present
Date: Fri, 27 Jan 2017 11:30:46 +0200 [thread overview]
Message-ID: <83mvec26k9.fsf@gnu.org> (raw)
In-Reply-To: <CADgGpBiN8vrHKZNj8vdcJWLqWm9-npAPdkG93zgFHYKQxi9OTg@mail.gmail.com> (message from Michael Hoffman on Mon, 23 Jan 2017 14:24:28 -0500)
> From: Michael Hoffman <hoffman@cantab.net>
> Date: Mon, 23 Jan 2017 14:24:28 -0500
> Cc: 11919@debbugs.gnu.org, Michael Hoffman <gmane3-hoffman@snkmail.com>
>
> See these messages in the archives for the reason why that change was
> done:
>
> https://lists.gnu.org/archive/html/emacs-pretest-bug/2005-11/msg00020.html
> https://lists.gnu.org/archive/html/emacs-pretest-bug/2005-11/msg00103.html
> https://lists.gnu.org/archive/html/emacs-pretest-bug/2005-12/msg00089.html
>
> If you can propose changes that solve this issue without
> re-introducing that one, please do.
>
> The below patch eliminates the garbage printing while maintaining the behavior added in 2005 of having
> `handled-ansi-message` preventing any updates to `default-directory` based on a \032 escape.
Thanks, I pushed this to the master branch, with a slight change due
to changes in the surrounding code since the version you were using.
Please test the master branch, if you can, and please reopen the bug
if some issues are left.
prev parent reply other threads:[~2017-01-27 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 0:45 bug#11919: 24.1; term-emulate-term does not process bash's Ctrl-Z signal of directory name when an AnSi message is present Michael Hoffman
2017-01-23 17:54 ` Michael Hoffman
2017-01-23 18:18 ` Eli Zaretskii
2017-01-23 18:30 ` Eli Zaretskii
2017-01-23 19:24 ` Michael Hoffman
2017-01-27 9:30 ` Eli Zaretskii [this message]
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=83mvec26k9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=0wdp3p2xrt@sneakemail.com \
--cc=11919-done@debbugs.gnu.org \
--cc=gmane3-hoffman@snkmail.com \
--cc=hoffman@cantab.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.