From: Marius Hofert <marius.hofert@math.ethz.ch>
To: help-gnu-emacs@gnu.org
Subject: How to suppress/avoid *Async Shell Command* buffer?
Date: Sat, 18 May 2013 02:03:21 +0200 [thread overview]
Message-ID: <87k3mx2lyu.fsf@math.ethz.ch> (raw)
Hi,
I use
--8<---------------cut here---------------start------------->8---
(setq dired-guess-shell-alist-user
'(("\\.\\(?:pdf\\|djvu\\|jp?g\\)\\'" "okular ? &")
("\\.html\\'" "google-chrome ? &")))
--8<---------------cut here---------------end--------------->8---
to open pdf files in dired-mode via "!". Once I do this, my dired buffer
is vertically divided into two pieces by opening a buffer named
*Async Shell Command*. The buffer does not show anything. It is quite
useless and *very* tedious to close (not only for pdf files). How can I
suppress this buffer / avoid this buffer being opened?
Here is what I found on this topic:
1)
http://stackoverflow.com/questions/3679930/how-to-automatically-remove-or-prevent-popping-up-async-shell-command-in-ema
2)
http://stackoverflow.com/questions/6915314/emacs-automatically-close-async-output-buffers-on-command-completion3)
http://stackoverflow.com/questions/12083228/how-do-i-speed-up-emacs-output-from-an-asynchronous-shell-command
4) http://stackoverflow.com/questions/13348230/create-buffer-and-immediately-hide-it
5) http://stackoverflow.com/questions/7298372/run-a-program-from-emacs-and-dont-wait-for-output
6) https://groups.google.com/forum/?fromgroups#!topic/gnu.emacs.help/TNqE7R7mULk
1), 2), 3): idea with save-window-excursion
4), 5): idea with start-process
6): call-process-shell-command
The problem is that I don't know how to *use* (one of) these approaches,
especially not with dired-mode's "!". Ideally, the buffer *Async Shell
Command* is not opened at all or at least is opened in the background
but does not 'destroy' (take up space from) the current buffer.
Cheers,
Marius
next reply other threads:[~2013-05-18 0:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 0:03 Marius Hofert [this message]
2013-05-18 8:48 ` How to suppress/avoid *Async Shell Command* buffer? Andreas Röhler
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 10:05 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
2013-05-18 14:39 ` Hongxu Chen
2013-05-18 18:52 ` Marius Hofert
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=87k3mx2lyu.fsf@math.ethz.ch \
--to=marius.hofert@math.ethz.ch \
--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).