From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>,
maurooaranda@gmail.com, emacs-devel@gnu.org
Subject: Re: Start of Emacs 30 release cycle
Date: Wed, 26 Jun 2024 08:53:52 +0200 [thread overview]
Message-ID: <87sex0xkhr.fsf@gmx.net> (raw)
In-Reply-To: <86bk3p9frm.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Jun 2024 18:57:33 +0300")
On Tue, 25 Jun 2024 18:57:33 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, maurooaranda@gmail.com, emacs-devel@gnu.org
>> Date: Tue, 25 Jun 2024 17:09:48 +0200
>>
>> Stephen> I haven't changed indent-tabs-mode: its global value is the default t
>> Stephen> but in buffers under emacs/lisp nil. And the diffs don't look
>> Stephen> funny to
>> Stephen> me; how do they look funny to you?
>>
>> eg this hunk:
>>
>> (defsubst widget-type (widget)
>> @@ -2452,10 +2475,16 @@ 'checkbox
>> (defun widget-checkbox-action (widget &optional event)
>> "Toggle checkbox, notify parent, and set active state of sibling."
>> (widget-toggle-action widget event)
>> - (let ((sibling (widget-get-sibling widget)))
>> + (let* ((sibling (widget-get-sibling widget))
>> + (from (widget-get sibling :from))
>> + (to (widget-get sibling :to)))
>>
>> Thereʼs a tab on the line for 'to', but the line for 'from' uses spaces.
Ah, right. I see things like that when I give the diff a close look,
but since the faces of whitespace-mode, though enabled, are not visible
in diff-mode (is this intended?), I often don't notice it.
> The original .dir-locals.el also has TABs.
And wid-edit.el is replete with tabs and spaces, so if I unintentionally
added a tab or two (but using only default settings for
emacs-lisp-mode), I don't think it significantly worsens the situation.
Steve Berman
next prev parent reply other threads:[~2024-06-26 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 13:44 Start of Emacs 30 release cycle Eli Zaretskii
2024-06-24 8:32 ` Stephen Berman
2024-06-24 12:47 ` Eli Zaretskii
2024-06-24 13:49 ` Stephen Berman
2024-06-24 15:05 ` Eli Zaretskii
2024-06-25 10:41 ` Stephen Berman
2024-06-25 13:48 ` Eli Zaretskii
2024-06-26 6:45 ` Stephen Berman
2024-06-25 14:10 ` Robert Pluim
2024-06-25 14:48 ` Stephen Berman
2024-06-25 15:09 ` Robert Pluim
2024-06-25 15:57 ` Eli Zaretskii
2024-06-26 6:53 ` Stephen Berman [this message]
2024-06-26 9:27 ` Robert Pluim
2024-07-01 13:15 ` nxml comments fix (was: Start of Emacs 30 release cycle) Konstantin Kharlamov
2024-07-01 13:41 ` Eli Zaretskii
2024-07-01 14:00 ` Konstantin Kharlamov
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 6:48 Start of Emacs 30 release cycle Pedro Andres Aranda Gutierrez
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=87sex0xkhr.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=maurooaranda@gmail.com \
--cc=rpluim@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).