GNU bug report logs - #75355
[PATCH 0/1] Improve comment cycling in log-edit

Previous Next

Full log

Message #31 received at 75355 <at> debbugs.gnu.org (full text, mbox):

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Jonas Bernoulli <jonas <at> bernoul.li>,
 75355 <at> debbugs.gnu.org
Subject: Re: bug#75355: [PATCH 1/1] Improve comment cycling in log-edit
Date: Fri, 14 Feb 2025 07:36:53 +0800

Hello,

On Thu 13 Feb 2025 at 01:48am -08, Stefan Kangas wrote:

> Sean Whitton <spwhitton <at> spwhitton.name> writes:
>
>> - I think some people might prefer not to have their half-written
>>   comment saved.  What do you think about doing everything in entries in
>>   log-edit-save-comment-hook, so that someone could customise that to
>>   remove the default behaviour, if they wanted?  Or perhaps a simple
>>   boolean defcustom to turn this new behaviour on and off.
>
> What would be the use case for not saving it?  IIUC, this is anyways
> just saved in memory, so is there any real drawback to just keeping it
> there?  If you don't care, you don't care, so to speak.

If M-p unexpectedly scrolls you into your half-finished comment instead
of into one you expect, you might hit C-c C-c before you realise and
create a broken commit.

I think sometimes one knows what the latest entry of one's comment ring
is (e.g. when you know you *just* cancelled a commit) and so it would be
jarring if M-p produced something else.

-- 
Sean Whitton

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.