From: Greg Troxel <gdt@lexort.com>
To: ding@gnus.org
Subject: gnus in emacs 26 ok?
Date: Sun, 02 Sep 2018 19:18:06 -0400 [thread overview]
Message-ID: <smubm9fjxox.fsf@linuxpal.mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
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.
I realize I should set debug-on-error and figure out what's going on,
but I don't know how to deal with ^G not working.
I also realize this report is lame and not actionable, but I wonder if
others have seen problems that might be similar or have advice.
Greg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2018-09-02 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 23:18 Greg Troxel [this message]
2018-09-04 14:12 ` Eric Abrahamsen
2018-09-04 15:15 ` Eric S Fraga
2018-09-04 23:25 ` Greg Troxel
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=smubm9fjxox.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).