From: dme@dme.org
Cc: ding@gnus.org
Subject: Re: CVS Gnus hangs on `gnus-summary-show-article'
Date: 16 Nov 2000 10:06:27 +0000 [thread overview]
Message-ID: <873dgs44f0.fsf@serafina-pekkala.dme.org> (raw)
In-Reply-To: <2ny9ykol29.fsf@tiger.jia.vnet>
* zsh@cs.rochester.edu [2000-11-15 23:46:38]
> > i updated to the latest CVS gnus. It seems to hang on the article
> > included below when pressing `gnus-summary-show-article' and also on
foo>> `gnus-summary-copy-article'. I waited up to 30 seconds for display (< 1
> > sec is normal), but nothing happens. So i set `toggle-debug-on-quit' and
> > quitted:
>
> Fixed. But message-cite-prefix-regexp is still problematic.
Expanding out the grouping for leading and trailing whitespace and
removing the combination stuff:
(setq message-cite-prefix-regexp
"[ \t]*\\(\\w\\|[_-\\.]\\)+>+[ \t]*\\|[ \t]*[]>»|:}+ ]*[]>»|:}+][ \t]*")
improves things a lot, but now interleaved supercite and non-supercite
citations aren't correctly detected by m-n-a-r.
I think that's a small price to pay.
dme.
next prev parent reply other threads:[~2000-11-16 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 21:38 Christoph Conrad
2000-11-15 23:46 ` ShengHuo ZHU
2000-11-16 10:06 ` dme [this message]
2000-11-16 13:38 ` ShengHuo ZHU
2000-11-16 19:27 ` Lee Cantey
2000-11-16 22:10 ` ShengHuo ZHU
2000-11-16 21:38 ` Lee Cantey
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=873dgs44f0.fsf@serafina-pekkala.dme.org \
--to=dme@dme.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).