From: Orm Finnendahl <finnendahl@folkwang-hochschule.de>
Subject: Re: shell-command without output
Date: Tue, 16 Dec 2003 10:47:06 +0100 [thread overview]
Message-ID: <20031216094706.GA1275@finnendahl.de> (raw)
In-Reply-To: <gypteqylm0.fsf@enquist.math.leidenuniv.nl>
Am 15. Dezember 2003, 19:36 Uhr (+0100) schrieb Miguel Frasson:
> I am writing a major mode (frontend for a script) and I want to execute
> shell commands, but *do not* read the output (unless I want, switching to an
> output buffer, for instance).
>
> shell-command always shows the output.
>
> How to avoid that (no matter the script has output or not)?
redirect the output of the shell command to /dev/null
(like '<command> &> /dev/null')
--
Orm
prev parent reply other threads:[~2003-12-16 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 18:36 shell-command without output Miguel Frasson
2003-12-15 18:48 ` Jesper Harder
2003-12-16 9:47 ` Orm Finnendahl [this message]
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=20031216094706.GA1275@finnendahl.de \
--to=finnendahl@folkwang-hochschule.de \
/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).