Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: ding@gnus.org
Subject: Re: gnus in emacs 26 ok?
Date: Tue, 04 Sep 2018 19:25:08 -0400	[thread overview]
Message-ID: <smush2o7smj.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <smubm9fjxox.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Sun, 02 Sep 2018 19:18:06 -0400")

Greg Troxel <gdt@lexort.com> writes:

> I just updated from emacs 25 to 26, and hence updated gnus.  I use gnus,
> against a dovecot imap server on localhost.  Generally things have been
> fine; I've been using gnus like this since about 2005.  Host is NetBSD,
> but that seems unlikely to matter.
>
> After updating, I am observing that on displaying some messages
> (articles :-) emacs seems to hang, and ^G results in seeing something
> that looks like source.  Another issue is that after typing 'f' to
> create a reply-all buffer, C-c C-y to quote the article results in 100%
> cpu usage with ^G not interrupting.

Thanks to all for the comments.  Some updates:

  I have gone from 26 to 25 and 24, being sure to rebuild all my
  out-of-emacs elc files (org, bbdb).  Didn't seem to help.

  I am no longer seeing the articles hanging, but I am seeing emacs at
  100% cpu after quoting an article ('f', 'c-c c-y').   I sent SIGUSR2,
  and got a backtrace showing font-lock.  This is repeatable.

  So my theory is that font-lock on-the-fly in a quoted reply is going
  bad.

  I've tried to reduce everything I could, and am flailing a bit, but
  commenting this out seems to have helped:
     ;(modify-syntax-entry ?_ "w" text-mode-syntax-table)
  I was trying to get foo_bar treated as a word (in c), and can live
  without that.

I'll check on the shr issue, and follow up if I find anything
definitive.



  parent reply	other threads:[~2018-09-04 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 23:18 Greg Troxel
2018-09-04 14:12 ` Eric Abrahamsen
2018-09-04 15:15 ` Eric S Fraga
2018-09-04 23:25 ` Greg Troxel [this message]
2018-09-05 13:25   ` Filipp Gunbin
2018-09-05 14:14     ` Greg Troxel

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=smush2o7smj.fsf@linuxpal.mit.edu \
    --to=gdt@lexort.com \
    --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).