From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] text/html => w3m?
Date: Tue, 29 Jan 2008 19:52:00 -0800 [thread overview]
Message-ID: <1201665031-sup-1818@south> (raw)
In-Reply-To: <1201636435-sup-5110@tangerine.lanl.gov>
Reformatted excerpts from John Bent's message of 2008-01-29:
> Hope this helps but I'm still learning sup too so this might all be
> wrong...
Pretty much right. Sup uses run-mailcap by default, which is where w3m
is being picked up on your system. So you can change your mailcap, or
you can override the hook. Depends on whether you want this change to be
system-wide or specific to Sup.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-01-30 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 19:33 Daniel Wagner
2008-01-29 19:59 ` John Bent
2008-01-29 21:45 ` Daniel Wagner
2008-01-30 3:52 ` 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=1201665031-sup-1818@south \
--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