--- Begin Message ---
Subject: |
Incorrect customization group for undo-no-redo |
Date: |
Fri, 14 Jan 2022 19:46:24 +0100 |
Tags: patch
In Emacs 28, undo-no-redo incorrectly uses the customization group
next-error. Can I install the attached patch on the emacs-28 branch to
fix this?
In GNU Emacs 28.0.91 (build 4, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, cairo
version 1.16.0)
of 2022-01-13
Repository revision: 34ca4ff9a52d38250f70f578fd045490b4eef4f9
Repository branch: emacs-28
Windowing system distributor 'The X.Org Foundation', version 11.0.12013000
System Description: Debian GNU/Linux rodete
Configured using:
'configure --enable-gcc-warnings=warn-only
--enable-gtk-deprecation-warnings --without-pop --with-mailutils
--enable-checking=all --enable-check-lisp-object-type --with-modules
'CFLAGS=-O0 -ggdb3''
0001-lisp-simple.el-undo-no-redo-Fix-customization-group.patch
Description: Text Data
--
Google Germany GmbH
Erika-Mann-Straße 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben
sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie
alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail
an die falsche Person gesendet wurde.
This e-mail is confidential. If you received this communication by mistake,
please don’t forward it to anyone else, please erase all copies and
attachments, and please let me know that it has gone to the wrong person.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#53266: Incorrect customization group for undo-no-redo |
Date: |
Fri, 14 Jan 2022 22:33:06 +0100 |
Am Fr., 14. Jan. 2022 um 20:02 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Fri, 14 Jan 2022 19:46:24 +0100
> >
> > In Emacs 28, undo-no-redo incorrectly uses the customization group
> > next-error. Can I install the attached patch on the emacs-28 branch to
> > fix this?
>
> Yes, thanks.
Thanks, done (commit 5990148860094bc3ad0ec55e4edac543d1c2036e).
--- End Message ---