From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Lindström" <bkhl@elektrubadur.se>,
"Stefan Kangas" <stefankangas@gmail.com>,
"Andrea Corallo" <acorallo@gnu.org>
Cc: 71499@debbugs.gnu.org
Subject: bug#71499: [PATCH] Make whitespace.el cleanup add missing final newline
Date: Wed, 12 Jun 2024 12:41:33 +0300 [thread overview]
Message-ID: <86cyom1os2.fsf@gnu.org> (raw)
In-Reply-To: <e49dc230-e376-40cf-b886-c009862c20af@app.fastmail.com> (message from Björn Lindström on Wed, 12 Jun 2024 11:04:18 +0200)
> Date: Wed, 12 Jun 2024 11:04:18 +0200
> From: Björn Lindström <bkhl@elektrubadur.se>
> Cc: 71499@debbugs.gnu.org
>
> On Wed, Jun 12, 2024, at 09:46, Eli Zaretskii wrote:
> >> Date: Tue, 11 Jun 2024 20:16:03 +0200
> >> From: Björn Lindström <bkhl@elektrubadur.se>
> >>
> > This is an incompatible change of behavior on behalf of
> > whitespace-cleanup, so I don't think we can accept it as in this patch
> > (or the next one you sent). Se we'd need some new user option, by
> > default off, to turn on this new feature. Or maybe a new action for
> > whitespace-action?
> >
> > Thanks.
>
> Hello,
>
> I thought about that, but since whitespace-cleanup generally applies clean-up according to white-space style, I thought it was simply an oversight that it doesn't apply a fix when it is set to highlight missing end-of-file newline.
>
> Adding a separate way to configure this removes the simplicity of configuring your preferred whitespace-style as a single option.
>
> However, If you still disagree I can make another patch somehow maintains the old behaviour as the default, so just let me know.
Let's see what others think, and take it from there.
Stefan, Andrea: WDYT about this change?
next prev parent reply other threads:[~2024-06-12 9:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 18:16 bug#71499: [PATCH] Make whitespace.el cleanup add missing final newline Björn Lindström
2024-06-12 5:21 ` Björn Lindström
2024-06-12 7:46 ` Eli Zaretskii
2024-06-12 9:04 ` Björn Lindström
2024-06-12 9:41 ` Eli Zaretskii [this message]
2024-06-12 12:38 ` Stefan Kangas
2024-06-13 7:38 ` Andrea Corallo
2024-06-13 8:30 ` Eli Zaretskii
2024-06-14 12:23 ` Robert Pluim
2024-06-14 12:50 ` Eli Zaretskii
2024-06-20 7:55 ` Stefan Kangas
2024-06-20 8:22 ` Robert Pluim
2024-06-20 8:55 ` Stefan Kangas
2024-06-20 9:45 ` Robert Pluim
2024-06-20 11:23 ` Stefan Kangas
2024-06-27 7:37 ` Eli Zaretskii
2024-06-29 11:59 ` Björn Lindström
2024-06-29 13:05 ` Eli Zaretskii
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=86cyom1os2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71499@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=bkhl@elektrubadur.se \
--cc=stefankangas@gmail.com \
/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).