From: "James H. Cloos Jr." <cloos@jhcloos.com>
Subject: Re: pgnus-0.74 - signal in ieft-drums-remove-comments()
Date: 04 Feb 1999 14:17:26 -0600 [thread overview]
Message-ID: <m3vhhhrkix.fsf@k6.jhcloos.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Feb 1999 02:10:51 +0100"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK. I was not seeing what I thought I was seeing.
Slowing it down by running it in edebug makes it clear. The same
Xface -- the correct one -- is displayed four times. Each time,
delete-process is called on the "article-x-face" process before
a new one is started, which explains the flashing xv(1)s. I'm
still not certain *why* it loops like that. Seems that
(when (stringp gnus-article-x-face-command)
(setq last t))
doesn't always set last.
But only due to somethign strange in message <yj9679rktir.fsf@adobe.com>.
I wonder whether it has anything to do with the fact that the 3rd body
part is a message/rfc822 but is declared to be text/plain and has name
and filename set to *Article*. (Incidently, is there a way to bypass
the asterisks-mean-bold behavior while composing a message?)
Anyway, the bug I thought I was seeing isn't there, and what is is
merely cosmetic, and I bet rare as a, err, um, .... (Well, whatever
it was I was going to write, it is so rare I've forgotten what it is
called. :) ((And you really don't think I could make up something
like that? Do you? Well, maybe. But not this time. Really.))
- -JimC
- --
James H. Cloos, Jr. <http://www.jhcloos.com/cloos/public_key> 1024D/ED7DAEA6
<cloos@jhcloos.com> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE2ugBUmXqfF+19rqYRAlwlAJ9X6pRpnpEIYIFHae1HCsE+/yLyhQCdF6Sn
gOamRnAmHomHFS8k3Yh87cc=
=lYp/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~1999-02-04 20:17 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
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. [this message]
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=m3vhhhrkix.fsf@k6.jhcloos.com \
--to=cloos@jhcloos.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).