From: Marius Hofert <marius.hofert@gmail.com>
To: andreas.roehler@easy-emacs.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to suppress/avoid *Async Shell Command* buffer?
Date: Sat, 18 May 2013 12:05:29 +0200 [thread overview]
Message-ID: <CAM3-Kjame2dbOuv2YDZfgGehAEW5F4Ec8W5FWhhKGtN69Zz8+g@mail.gmail.com> (raw)
Hi Andreas,
Thanks a lot for helping.
The purpose is simply for opening them (asynchronously), viewing the pdf
(continuing to work in Emacs), (maybe add annotations to the pdf and save
it).
I use 'dired-mode' as 'file manager' and often would like to open and view
pdfs in Okular. I also have other 'dired-guess-shell-alist-user' settings
like opening pngs in eog or mp3s in VLC. But everytime I open a file, I get
this annoying *Async Shell Command* buffer (either empty or with debug
output) and I have to manually close it via C-x 0 etc. to get rid of it. I
know that it might contain useful information sometimes and I wouldn't be
against it appearing hidden (in the buffer list). But being distracted by
this buffer in dired-mode is really unpleasant. If I only knew more emacs
lisp...
Cheers,
Marius
next reply other threads:[~2013-05-18 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 10:05 Marius Hofert [this message]
2013-05-18 12:47 ` How to suppress/avoid *Async Shell Command* buffer? 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
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM3-Kjame2dbOuv2YDZfgGehAEW5F4Ec8W5FWhhKGtN69Zz8+g@mail.gmail.com \
--to=marius.hofert@gmail.com \
--cc=andreas.roehler@easy-emacs.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.
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.