From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37068 Path: main.gmane.org!not-for-mail From: ShengHuo ZHU Newsgroups: gmane.emacs.gnus.general Subject: Re: BUG: mm-display-external requires an xterm Date: Tue, 24 Jul 2001 10:53:01 -0700 Sender: zsh@piglet.jia.vnet Message-ID: <2n8zhe6woy.fsf@piglet.jia.vnet> References: <87ofqqko93.fsf@squeaker.lickey.com> <2nu20hpv08.fsf@piglet.jia.vnet> <8766cwg0k7.fsf@squeaker.lickey.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172548 11928 80.91.224.250 (21 Oct 2002 03:55:48 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:55:48 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 18509 invoked from network); 24 Jul 2001 17:55:44 -0000 Original-Received: from unknown (HELO zsh.2y.net) (131.241.79.246) by gnus.org with SMTP; 24 Jul 2001 17:55:44 -0000 Original-Received: (from zsh@localhost) by zsh.2y.net (8.11.2/8.11.2) id f6OHr2m04434; Tue, 24 Jul 2001 10:53:02 -0700 Original-To: ding@gnus.org X-Attribution: ZSH X-Face: 'IF:e51ib'Qbl^(}l^&4-J`'P!@[4~O|&k#:@Gld#b/]oMq&`&FVY._3+b`mzp~Jeve~/#/ ERD!OTe<86UhyN=l`mrPY)M7_}`Ktt\K+58Z!hu7>qU,i.N7TotU[FYE(f1;}`g2xj!u*l`^&=Q!g{ *q|ddto|nkt"$r,K$[)"|6,elPH= GJ6Q User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104 Original-Lines: 37 Xref: main.gmane.org gmane.emacs.gnus.general:37068 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37068 Matt Armstrong writes: > ShengHuo ZHU writes: > >> Matt Armstrong 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. > > Good idea. Now I have two more problems. :-) > > 1) The new term.el stuff is a little buggy. If it shows html, it > launches lynx (actually w3m) in a buffer called *display* but does > not make *display* visible, so it stays burried below the empty > *Article* buffer. > > When I switch to the *display* buffer, I see the html, but when I > quit w3m I'm left with a dead *display* buffer. Maybe it should > switch back to the *Article* buffer? Or kill the *display* buffer? > > When I switch to the *Summary* buffer, things are broken. I can't > select the next article -- it starts raising errors related to the > *Article* buffer. I know this is a bad bug report -- I can narrow > it down when I have more time if needed. Fixed. ShengHuo