From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46116@debbugs.gnu.org, Jonathan Corbet <corbet@lwn.net>
Subject: bug#46116: 28.0.50; Ticking articles fails on Emacs 28 pgtk/native-comp build
Date: Wed, 27 Jan 2021 07:08:49 +0100 [thread overview]
Message-ID: <87k0rykj2m.fsf_-_@gmail.com> (raw)
In-Reply-To: <87lfcff93h.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 27 Jan 2021 02:43:14 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I'm unable to reproduce this in Emacs 28, and it sounds very strange
> (because this is pretty basic functionality). Do you have any
> customisations in this area?
Cf. <20210126150026.4d5e0e96@lwn.net>: jon happens to also run
--with-native-comp, which he suspects might be the culprit; this does
sound more likely than --with-pgtk, especially given the workaround he
describes (manually running eval-defun on gnus-summary-goto-subjet).
(Changing the Subject to reflect this)
prev parent reply other threads:[~2021-01-27 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 17:00 bug#46116: 28.0.50; Ticking articles fails on Emacs 28 pgtk build Jonathan Corbet
[not found] ` <handler.46116.B.161168302225070.ack@debbugs.gnu.org>
2021-01-26 22:00 ` bug#46116: Acknowledgement (28.0.50; Ticking articles fails on Emacs 28 pgtk build) Jonathan Corbet
2021-01-27 9:29 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-27 17:54 ` Jonathan Corbet
2021-01-27 20:37 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-27 21:57 ` Jonathan Corbet
2021-01-28 7:58 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28 23:48 ` Jonathan Corbet
2021-01-29 8:50 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-27 1:43 ` bug#46116: 28.0.50; Ticking articles fails on Emacs 28 pgtk build Lars Ingebrigtsen
2021-01-27 6:08 ` Kévin Le Gouguec [this message]
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=87k0rykj2m.fsf_-_@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=46116@debbugs.gnu.org \
--cc=corbet@lwn.net \
--cc=larsi@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.