unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: john muhl <jm@pub.pink>, stephen.berman@gmx.net
Cc: 72404@debbugs.gnu.org, maurooaranda@gmail.com, juri@linkov.net
Subject: bug#72404: 30.0.60; Customization of options is broken
Date: Thu, 01 Aug 2024 08:09:52 +0300	[thread overview]
Message-ID: <867cd0ygkf.fsf@gnu.org> (raw)
In-Reply-To: <87le1hs1s2.fsf@pub.pink> (message from john muhl on Wed, 31 Jul 2024 15:18:46 -0500)

> From: john muhl <jm@pub.pink>
> Cc: Juri Linkov <juri@linkov.net>,  Mauro Aranda <maurooaranda@gmail.com>,
>   72404@debbugs.gnu.org,  stephen.berman@gmx.net
> Date: Wed, 31 Jul 2024 15:18:46 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> 0. emacs-30 -Q
> >> 1. Eval: (require 'log-edit)
> >> 2. Check the value of 'log-edit-hook'.
> >>    Its value is
> >>    (log-edit-insert-message-template log-edit-insert-cvs-template log-edit-insert-changelog log-edit-show-files)
> >> 3. M-x customize-variable RET log-edit-hook RET
> >> 4. Click the checkbox to enable 'log-edit-insert-cvs-rcstemplate'.
> >> 5. Apply
> >> 6. Check the value of 'log-edit-hook'.
> >>    Its value is (log-edit-insert-cvs-rcstemplate)
> >> 
> >> In GNU Emacs 30.0.60 (build 1, x86_64-pc-linux-gnu, X toolkit,
> >>  cairo version 1.16.0, Xaw3d scroll bars) of 2024-07-31
> >> Repository revision: ceb5a1522270c41d0c9f5e6b52d61e3173f72f1d
> >> Repository branch: emacs-30
> >> Windowing system distributor 'The X.Org Foundation', version 11
> >> Configured using: 'configure --with-native-compilation --with-x-toolkit=lucid'
> >> 
> >> Whereas in GNU Emacs 29.3.50 it was correctly changed to
> >> (log-edit-insert-message-template log-edit-insert-cvs-rcstemplate
> >> log-edit-insert-cvs-template log-edit-insert-changelog log-edit-show-files)
> >
> > Thanks.  Bisection would be useful, I think.
> >
> > Adding Mauro, in case he has some ideas or even fixes.
> 
> Reverting 8d354925ddb fixes it here.

Thanks!

Stephen, please look at this ASAP, as this sounds like a serious
and very recent regression.





  reply	other threads:[~2024-08-01  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 17:25 bug#72404: 30.0.60; Customization of options is broken Juri Linkov
2024-07-31 18:04 ` Eli Zaretskii
2024-07-31 20:18   ` john muhl
2024-08-01  5:09     ` Eli Zaretskii [this message]
2024-08-01 10:12       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-01 17:28         ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04  7:49           ` Eli Zaretskii
2024-08-04 10:00             ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867cd0ygkf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72404@debbugs.gnu.org \
    --cc=jm@pub.pink \
    --cc=juri@linkov.net \
    --cc=maurooaranda@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).