From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: BUG: mm-display-external requires an xterm
Date: Thu, 12 Jul 2001 16:50:31 -0700 [thread overview]
Message-ID: <2nu20hpv08.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <87ofqqko93.fsf@squeaker.lickey.com> (Matt Armstrong's message of "Thu, 12 Jul 2001 11:15:20 -0700")
Matt Armstrong <matt@lickey.com> writes:
> When mm-display-external decides that a mailcap entry needs a
> terminal, it unconditionally fires off "xterm". There are two
> problems:
>
> 1) It tries to run the xterm even if window-system is nil.
>
> My mailcap has text/html being shown with lynx. If I'm running
> emacs within an xterm, shouldn't emacs just temporarily shell out
> to lynx?
I've fixed it in the Gnus CVS. term.el is used for running lynx.
> 1) What if I want rxvt instead? Or maybe ETerm? Perhaps there should
> be a gnus-external-terminal variable. This is minor.
mm-external-terminal-program is added.
ShengHuo
next prev parent reply other threads:[~2001-07-12 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 18:15 Matt Armstrong
2001-07-12 23:50 ` ShengHuo ZHU [this message]
2001-07-13 18:12 ` Matt Armstrong
2001-07-13 21:00 ` Colin Walters
2001-07-24 17:53 ` ShengHuo ZHU
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=2nu20hpv08.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.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;
as well as URLs for NNTP newsgroup(s).