unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Andreas Politz <politza@fh-trier.de>
To: help-gnu-emacs@gnu.org
Subject: Re: ^M chars in *Async Command Output*
Date: Fri, 23 Jan 2009 10:37:18 +0100	[thread overview]
Message-ID: <1232703501.688012@arno.fh-trier.de> (raw)
In-Reply-To: <mailman.5557.1232699065.26697.help-gnu-emacs@gnu.org>

Sebastian Tennant wrote:
> Hi all,
> 
> When I issue asynchronous commands using shell-command, for example:
> 
>   M-! apt-get update & RET
> 
> buffer *Async Command Output* is filled with ^M characters and the
> output is generally a mess.
> 
> Apparently not all Emacsen behave in this way though.
> 
> If you have a moment, could you perform a similar test and let us know
> if the same thing happens to you.  Include the Emacs version number in
> your follow-up, and if it _does_ happen to you and you have a little
> more time, whether you consider it a feature or a bug?
> 
> Your assistance is much appreciated.
> 
> Sebastian

I tried it with aptitude, it's the same. The process uses carriage-returns
to display the progress `widget' this show up as '^M' in emacs buffer.
Somehow this processes think they are running in a terminal, I think
because asynchronous shell-commands are runnning/started in a shell.

In a terminal :

$ echo -e 'Hello\rWorld'
$ World

In emacs :

M-! echo -e 'Hello\rWorld' &
Hello ^MWorld

Maybe a process-filter-function is the solution or pipe the command
through the utility 'col', like
M-! apt-get update | col &

-ap



       reply	other threads:[~2009-01-23  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5557.1232699065.26697.help-gnu-emacs@gnu.org>
2009-01-23  9:37 ` Andreas Politz [this message]
2009-01-23  9:42   ` ^M chars in *Async Command Output* Andreas Politz
2009-01-23 10:25   ` Sebastian Tennant
     [not found]     ` <mailman.5625.1232778837.26697.help-gnu-emacs@gnu.org>
2009-01-24  8:25       ` Andreas Politz
2009-01-25 17:41         ` Sebastian Tennant
2009-01-23  8:25 Sebastian Tennant

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=1232703501.688012@arno.fh-trier.de \
    --to=politza@fh-trier.de \
    --cc=help-gnu-emacs@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.
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).