From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55040@debbugs.gnu.org
Subject: bug#55040: 29.0.50; Auto-indent-mode and Changelog Messages
Date: Wed, 20 Apr 2022 17:08:20 +0000 [thread overview]
Message-ID: <87levzy96j.fsf@posteo.net> (raw)
In-Reply-To: <83tuanspwz.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Apr 2022 19:03:24 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Date: Wed, 20 Apr 2022 14:30:17 +0000
>>
>>
>> When writing change logs in log-edit-mode, I have auto-fill-mode enabled
>> because 1. I find it convenient and 2. it derives from text mode. It
>> has been pointed out to me that this leads to indentation issues, where
>> a change log entry is interpreted to be an unordered list. So instead
>> of
>>
>> --8<---------------cut here---------------start------------->8---
>> * lisp/vc/diff-mode.el (diff-add-log-current-defuns): Check
>> vc-root-dir to prepend the project path to the file being modified.
>> --8<---------------cut here---------------end--------------->8---
>>
>> the messages is automatically formatted like
>>
>> --8<---------------cut here---------------start------------->8---
>> * lisp/vc/diff-mode.el (diff-add-log-current-defuns): Check
>> vc-root-dir to prepend the project path to the file being modified.
>> --8<---------------cut here---------------end--------------->8---
>>
>> as soon as the line exceeds the fill column.
>
> I always use auto-fill-mode in ChangeLog buffers, and it never does
> anything like what you described for me. Can you show a recipe
> starting from "emacs -Q" that shows this problem?
1. Start emacs -Q
2. Open any versioned file
3. Make any modification
4. Prepare a commit using C-x v v
5. Go to the commit body and insert ChangeLog template
6. Ensure that auto-fill-mode is enabled in the buffer
7. Type anything until the fill-column is reached
I did 7. by just repeating the word "word", and after a short while it
auto-filled the line and the text appeared formatted as described above.
--
Philip Kaludercic
next prev parent reply other threads:[~2022-04-20 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:30 bug#55040: 29.0.50; Auto-indent-mode and Changelog Messages Philip Kaludercic
2022-04-20 16:03 ` Eli Zaretskii
2022-04-20 17:08 ` Philip Kaludercic [this message]
2022-04-20 17:28 ` Eli Zaretskii
2022-04-20 17:42 ` Philip Kaludercic
2022-04-20 18:31 ` Eli Zaretskii
2022-04-20 19:22 ` Eli Zaretskii
2022-04-20 20:59 ` Philip Kaludercic
2022-04-21 5:40 ` Eli Zaretskii
2022-04-22 14:36 ` Lars Ingebrigtsen
2022-04-22 15:36 ` Eli Zaretskii
2022-04-23 12:22 ` Lars Ingebrigtsen
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=87levzy96j.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=55040@debbugs.gnu.org \
--cc=eliz@gnu.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 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).