Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Pavel Zhukov <pavel.y.zhukov@gmail.com>
To: info-gnus-english@gnu.org
Subject: gnus is hanging on cite-parse
Date: Thu, 7 Sep 2017 06:27:06 -0700 (PDT)	[thread overview]
Message-ID: <807e339e-847a-49e0-a0f0-7abeb81055e1@googlegroups.com> (raw)

Hello,

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). 

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()
  gnus-cite-parse-wrapper()
  gnus-cite-parse-maybe(nil t)
  gnus-dissect-cited-text()
  gnus-article-fill-cited-article(nil t)
  gnus-article-fill-cited-long-lines()
  gnus-treat-article(nil 1 1 "text/plain")
  gnus-display-mime()
  gnus-article-prepare-display()
  gnus-article-prepare(218 nil)
  gnus-summary-display-article(218 nil)
  gnus-summary-select-article(nil nil pseudo)
  gnus-summary-scroll-up(1)
  funcall-interactively(gnus-summary-scroll-up 1)
  call-interactively(gnus-summary-scroll-up nil nil)
  command-execute(gnus-summary-scroll-up)

             reply	other threads:[~2017-09-07 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 13:27 Pavel Zhukov [this message]
2017-09-08  1:25 ` yamaoka
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=807e339e-847a-49e0-a0f0-7abeb81055e1@googlegroups.com \
    --to=pavel.y.zhukov@gmail.com \
    --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).