From: Andreas Schwab <schwab@linux-m68k.org>
To: Leo <sdl.web@gmail.com>
Cc: 6691@debbugs.gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>,
John Wiegley <johnw@newartisans.com>
Subject: bug#6691: 23.2; Eshell and ^M
Date: Sat, 14 Apr 2012 10:22:47 +0200 [thread overview]
Message-ID: <m24nsmen8o.fsf@linux-m68k.org> (raw)
In-Reply-To: <m1aa2ezrcf.fsf@gmail.com> (Leo's message of "Sat, 14 Apr 2012 15:48:32 +0800")
Leo <sdl.web@gmail.com> writes:
> The known fact is if I remove eshell-handle-control-codes from
> eshell-output-filter-functions, then I can observe outputting ^M in both
> GNU/Linux and OSX.
>
> So I think eshell-handle-control-codes might be where the problem is.
The point of eshell-handle-control-codes is to handle ^M (and other
control chars) like a terminal does.
(That its implementation is pretty inefficient is different issue.)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-04-14 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 15:09 bug#6691: 23.2; Eshell and ^M Leo
2010-07-22 15:30 ` bug#6691: 23.2; Eshell and ^M (PATCH attached) Leo
2012-04-11 11:16 ` Lars Magne Ingebrigtsen
2012-04-12 0:40 ` John Wiegley
2012-04-12 12:27 ` Lars Magne Ingebrigtsen
2012-04-12 13:35 ` John Wiegley
2012-04-12 1:23 ` bug#6691: 23.2; Eshell and ^M Glenn Morris
2012-04-14 7:48 ` Leo
2012-04-14 8:22 ` Andreas Schwab [this message]
2012-04-14 8:58 ` Eli Zaretskii
2012-04-14 9:16 ` Andreas Schwab
2012-04-14 8:27 ` Andreas Schwab
2012-04-14 8:33 ` Leo
2012-04-14 8:53 ` Andreas Schwab
2012-04-16 12:19 ` Leo
2012-04-16 13:45 ` Andreas Schwab
2012-04-16 13:59 ` Leo
2013-06-13 6:50 ` Glenn Morris
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=m24nsmen8o.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=6691@debbugs.gnu.org \
--cc=johnw@newartisans.com \
--cc=larsi@gnus.org \
--cc=sdl.web@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 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.