From: Emanuel Berg <incal@dataswamp.org>
To: ding@gnus.org
Subject: possible Gnus cite bug
Date: Mon, 26 Jun 2023 02:50:41 +0200 [thread overview]
Message-ID: <87wmzrt5b2.fsf@dataswamp.org> (raw)
I just saw a strange thing. I type this in a message mode
buffer just before sending, I observe that
>>> this is, correctly, `gnus-cite-3'
but
> '> this is also `gnus-cite-3'
but should be, IINM, `gnus-cite-1', as in
> this.
The syntax "> '>" doesn't make any sense but it doesn't mean
it makes sense to font lock it has `gnus-cite-3', if
you agree.
--
underground experts united
https://dataswamp.org/~incal
reply other threads:[~2023-06-26 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87wmzrt5b2.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=ding@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).