From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: philipk@posteo.net, 55040@debbugs.gnu.org
Subject: bug#55040: 29.0.50; Auto-indent-mode and Changelog Messages
Date: Fri, 22 Apr 2022 18:36:27 +0300 [thread overview]
Message-ID: <83k0bhp1tw.fsf@gnu.org> (raw)
In-Reply-To: <87ilr1w5gp.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 22 Apr 2022 16:36:06 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Philip Kaludercic <philipk@posteo.net>, 55040@debbugs.gnu.org
> Date: Fri, 22 Apr 2022 16:36:06 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > Looks like just turning off adaptive-fill-mode is enough to solve your
> >> > problem.
> >>
> >> Should it be disabled for log-edit-mode in general?
> >
> > Maybe. I'd be interested in hearing opinions of others, since
> > different projects have different conventions wrt this.
> >
> > Also, log-edit-mode doesn't turn on auto-fill-mode by default, so
> > maybe the change you propose should only be in effect if the user does
> > turn on auto-fill.
>
> I think having adaptive-fill-mode switched off would be an improvement
> when doing ChangeLog-like commits, but I'm not sure that it's a good
> idea in general.
>
> If we could instead make the adaptive filling smarter (and discover that
> we're doing a ChangeLog-like paragraph), that would be better, I think?
I'm not sure adaptive-fill-mode makes sense in log-edit-mode (since
AFAIU lines are supposed to be flushed to the left margin), but I
don't object to trying to solve this in some other way.
next prev parent reply other threads:[~2022-04-22 15:36 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
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 [this message]
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=83k0bhp1tw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55040@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=philipk@posteo.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).