Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: yamaoka@jpl.org
To: info-gnus-english@gnu.org
Subject: Re: gnus is hanging on cite-parse
Date: Thu, 7 Sep 2017 18:25:08 -0700 (PDT)	[thread overview]
Message-ID: <0e702c34-43f6-43dc-b5d3-e2ba585af215@googlegroups.com> (raw)
In-Reply-To: <807e339e-847a-49e0-a0f0-7abeb81055e1@googlegroups.com>

On Thu, 07 Sep 2017 06:27:06 -0700, Pavel Zhukov wrote:
> I have problem with gnus displaying some messages like described in
> [1] In my case traceback looks like [2]. As a workaround I use cite
> regexp like (setq message-cite-prefix-regexp ">") but it's not
> a solution.
> The problem occurs if I try to open this email
> https://lists.isc.org/pipermail/dhcp-users/2017-September/020820.html
> for example (and many many others).

I got the email from
<https://lists.isc.org/pipermail/dhcp-users/2017-September.txt.gz>
and tried reading it using Gnus, but no such a problem happened.

> Can somebody point me out what's wrong with the citation/regexp and
> how to fix that? Or how to debug the issue further.

> [1]  https://lists.gnu.org/archive/html/info-gnus-english/2017-01/msg00006.html

> [2]
> Debugger entered--Lisp error: (quit)
>   looking-at("^\\(\\([ 	]*\\(\\w\\|[_.]\\)+>+\\|[ 	]*[]>|]\\)+\\)? *>>>>> +\"\\([^\"\n]+\\)\" +==")
>   gnus-cite-parse()
[...]

The operand of `looking-at' is the same as the one I use, that
is just the default value of `gnus-supercite-regexp'.  Well,
what does happen when you evaluate this form at every beginning
of line one by one in that article body?

M-: (looking-at gnus-supercite-regexp) RET

  reply	other threads:[~2017-09-08  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 13:27 Pavel Zhukov
2017-09-08  1:25 ` yamaoka [this message]
2019-06-10  9:52   ` Van L

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=0e702c34-43f6-43dc-b5d3-e2ba585af215@googlegroups.com \
    --to=yamaoka@jpl.org \
    --cc=info-gnus-english@gnu.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).