From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] run-mailcap not working correctly
Date: Tue, 30 Oct 2007 19:29:29 -0500 [thread overview]
Message-ID: <1193790417-sup-3611@chris-tablet> (raw)
In-Reply-To: <1193783673-sup-4792@south>
Excerpts from William Morgan's message of Tue Oct 30 17:35:31 -0500 2007:
> Excerpts from Pierre Baillet's message of Tue Oct 16 01:19:38 -0700 2007:
> > I got the same issue on my debian setup here. Removing the >&... made
> > the html attachement work again.
> Is this some shell-specific thing? It seems to work on bash. If so, is
> there a portable way of discarding stderr? I don't want it cluttering
> the screen if the process fails.
Yes. In bash &> redirects both stdout and stderr. In sh, you can use this:
process > /dev/null 2> /dev/null
(From http://tomecat.com/jeffy/tttt/shredir.html)
Don't know about csh, ksh, &c.
--
Christopher Warrington <chrisw at rice.edu>
next prev parent reply other threads:[~2007-10-31 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 1:25 Ian Taylor
2007-10-16 8:19 ` Pierre Baillet
2007-10-30 22:35 ` William Morgan
2007-10-31 0:29 ` Christopher Warrington [this message]
2007-11-06 22:59 ` William Morgan
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=1193790417-sup-3611@chris-tablet \
--to=chrisw@rice.edu \
/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