From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: One-line summary
Date: 06 Nov 1999 02:58:41 +0100 [thread overview]
Message-ID: <m3ogd85qjy.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <u3dvx681k.fsf@lanber.cam.citrix.com>
Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> Good memory! This *is* a Gnus bug AFAICS (perhaps it needs to change
> symbol tables in that code). My workaround was simply to not use
> "%>", but that's not what I'd want in a perfect world.
The %< %> specs were taken by the new balloon-help thing, which made
things go wonky.
I've now moved these specs to %« and %», which is obviously a bad
idea, but all the other parenthesis-thingies were taken. Ideas?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-11-06 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-11 12:49 Toby Speight
1999-09-24 18:02 ` Lars Magne Ingebrigtsen
1999-09-24 23:49 ` Toby Speight
1999-09-27 20:23 ` Aaron M. Ucko
1999-09-29 15:39 ` Toby Speight
1999-11-06 1:58 ` Lars Magne Ingebrigtsen [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-11 12:36 Toby Speight
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=m3ogd85qjy.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).