From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] run-mailcap weirdness
Date: Mon, 27 Oct 2008 19:17:08 -0700 [thread overview]
Message-ID: <1225160150-sup-916@entry> (raw)
In-Reply-To: <1225046594-sup-8381@gillespie.rupamsunyata.org>
Reformatted excerpts from Decklin Foster's message of 2008-10-26:
> I don't know if this is right, but removing the redirection makes it work
> for me (I've committed this to decklins-clone at Gitorious). What was the
> original rationale for /dev/null-ing this? I noticed if you set the mailcap
> command to something that just prints text (no pager) it blips by
> instantaneously in Sup.
The original rationale was to stop it from screwing up the screen, but
I'd rather have it work in the first place.
I've merged in your commit. Thanks!
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-10-28 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 18:48 Decklin Foster
2008-10-28 2:17 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1225160150-sup-916@entry \
--to=wmorgan-sup@masanjin.net \
/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