all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 6691@debbugs.gnu.org, John Wiegley <johnw@newartisans.com>,
	Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: bug#6691: 23.2; Eshell and ^M
Date: Sat, 14 Apr 2012 15:48:32 +0800	[thread overview]
Message-ID: <m1aa2ezrcf.fsf@gmail.com> (raw)
In-Reply-To: <13zkahagk7.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 11 Apr 2012 21:23:52 -0400")

On 2012-04-12 09:23 +0800, Glenn Morris wrote:
> Are you sure this is related to `eshell-last-output-block-begin'?
> IIRC, there are various reports to do with extraneous ^M characters on
> Macs (eg with gdb). FWIW, I don't seem to see the problem you describe
> on GNU/Linux.

I have forgotten much about the reasoning behind the patch. So I am not
sure it is the right fix.

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.

BTW, why process coding system for input and output are set to
utf-8-unix? I bind coding-system-for-read to utf-8 and observe correct
output with nearly no ^M, i.e. no need to remove ^M after the fact.

Leo





  reply	other threads:[~2012-04-14  7:48 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 [this message]
2012-04-14  8:22     ` Andreas Schwab
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=m1aa2ezrcf.fsf@gmail.com \
    --to=sdl.web@gmail.com \
    --cc=6691@debbugs.gnu.org \
    --cc=johnw@newartisans.com \
    --cc=larsi@gnus.org \
    --cc=rgm@gnu.org \
    /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.