From: Danny Siu <dsiu@Adobe.COM>
Subject: Re: pgnus-0.74 - signal in ieft-drums-remove-comments()
Date: 29 Jan 1999 11:09:44 -0800 [thread overview]
Message-ID: <yj9ww25hp53.fsf@adobe.com> (raw)
In-Reply-To: "James H. Cloos Jr."'s message of "28 Jan 1999 16:40:18 -0600"
James H Cloos writes:
James> Check out the display of the referenced article in gnu emacs with
James> gnus-treat-display-xface set to t....
James> (Cf next page for spoiler:)
James> \f
James> The ref'ed article has an xface header, but also has a 822
James> attatchment which has an xface header. At least in pgnus-0.73 in
James> emacs 20.3.1, xv pops up with the first xface, quits w/o user
James> interaction and then pops up with the second xface.
James> The xface headers in attatchments probably shouldn't be
James> auto-displayed unless and until the attachment is viewed, ja?
I don't think that is the cause. ieft-drums-remove-comments() still signals
when gnus-treat-display-xface is set to t. Also, I am using xemacs-20.4 so
xv shouldn't pop up with xface.
James> -JimC -- James H. Cloos, Jr.
James> <http://www.jhcloos.com/cloos/public_key> 1024D/ED7DAEA6
James> <cloos@jhcloos.com> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D
James> AEA6
--
Danny Dick-Fung Siu mailto:dsiu@adobe.com
Acrobat Engineering @ Adobe Systems Incorporated
http://www.csua.berkeley.edu/~dsiu
next prev parent reply other threads:[~1999-01-29 19:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-28 20:54 Danny Siu
1999-01-28 22:40 ` James H. Cloos Jr.
1999-01-29 19:09 ` Danny Siu [this message]
1999-02-01 20:54 ` Lars Magne Ingebrigtsen
1999-02-02 1:34 ` James H. Cloos Jr.
1999-02-02 20:53 ` Lars Magne Ingebrigtsen
1999-02-02 23:05 ` James H. Cloos Jr.
1999-02-03 1:19 ` Lars Magne Ingebrigtsen
1999-02-03 16:21 ` James H. Cloos Jr.
1999-02-03 23:12 ` Lars Magne Ingebrigtsen
1999-02-04 0:05 ` James H. Cloos Jr.
1999-02-04 1:10 ` Lars Magne Ingebrigtsen
1999-02-04 20:17 ` James H. Cloos Jr.
1999-02-09 14:53 ` Lars Magne Ingebrigtsen
1999-02-01 20:58 ` Lars Magne Ingebrigtsen
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=yj9ww25hp53.fsf@adobe.com \
--to=dsiu@adobe.com \
/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).