From: Marius Hofert <marius.hofert@math.ethz.ch>
To: "Barry Margolin" <barmar@alum.mit.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to suppress/avoid *Async Shell Command* buffer?
Date: Sat, 18 May 2013 23:19:33 +0200 [thread overview]
Message-ID: <87d2sox9y2.fsf@math.ethz.ch> (raw)
In-Reply-To: <barmar-093865.13481518052013@news.eternal-september.org>
Barry Margolin writes:
> In article <mailman.41.1368897044.22516.help-gnu-emacs@gnu.org>,
> Andreas Röhler <andreas.roehler@easy-emacs.de> wrote:
>
>> Am 18.05.2013 16:37, schrieb Marius Hofert:
>> > Hi Andreas,
>> >
>> > what do you mean by 'caused'?
>> >
>> > The question mark is a place holder for the file (foo.pdf).
>>
>> Okay, see dired-do-shell-command reads it
>>
>> > What does this have to do with *Async Shell Command* being opened?
>> >
>>
>> Nothing. It's the ampersand following ? which matters.
>>
>> > Note: The behavior of "!" on foo.pdf in dired mode is fine (in the sense
>> > that Okular opens, the pdf is shown, everything asynchronously), I just want
>> > to avoid the buffer *Async Shell Command* being opened.
>> >
>>
>> Which seems the buffer Emacs connects the process to.
>> Deleting it should end the processes, probably not a good idea.
>>
>> So the ampersand seems the culprit - not the question mark.
>> What happens when calling your stuff without it?
>
> This is essentially the same as using M-!, isn't it, except that it
> automatically fills in the filename argument? If you don't use the
> ampersand, Emacs waits for the command to finish, and then displays the
> output in *Shell Command Output*. If you use ampersand, it doesn't wait,
> and displays the output incrementally in *Async Shell Command*.
>
> Either way, the output has to be put somewhere.
>
> However, the synchronous mode has a feature: if the command produces
> little or no output, it doesn't switch to the *Shell Command Output*
> buffer, it just displays it in the minibuffer. Here's a trick that I
> think should do what you want: Run the backgrounded command in a
> subshell (wrap it in parentheses):
>
> ! (command ? &>/dev/null &)
indeed, this also works, very nice!
Thanks, Barry.
Cheers,
Marius
>
>
> As far as Emacs is concerned, that's a synchronous command, because it
> doesn't end in "&". But it runs in the background within the subshell.
> Redirect the output so that Emacs immediately reads EOF, and has nothing
> to display in the minibuffer (it may display "(Shell command completed
> with no output)").
next prev parent reply other threads:[~2013-05-18 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 10:05 How to suppress/avoid *Async Shell Command* buffer? Marius Hofert
2013-05-18 12:47 ` Andreas Röhler
2013-05-18 13:58 ` Marius Hofert
2013-05-18 14:33 ` Andreas Röhler
2013-05-18 14:37 ` Marius Hofert
2013-05-18 17:13 ` Andreas Röhler
2013-05-18 18:03 ` Marius Hofert
2013-05-18 18:58 ` Andreas Röhler
[not found] ` <mailman.41.1368897044.22516.help-gnu-emacs@gnu.org>
2013-05-18 17:48 ` Barry Margolin
2013-05-18 21:19 ` Marius Hofert [this message]
2013-05-18 14:39 ` Hongxu Chen
2013-05-18 18:52 ` Marius Hofert
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 0:03 Marius Hofert
2013-05-18 8:48 ` Andreas Röhler
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=87d2sox9y2.fsf@math.ethz.ch \
--to=marius.hofert@math.ethz.ch \
--cc=barmar@alum.mit.edu \
--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).