unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: New branch feature/named-lambdas.
Date: Tue, 18 Jul 2023 11:14:17 +0000	[thread overview]
Message-ID: <ZLZ0CabjSHdbNJF-@ACM> (raw)
In-Reply-To: <ZLW0pTIn-JmPlYru@ACM>

Hello, Philip.

On Mon, Jul 17, 2023 at 21:37:41 +0000, Alan Mackenzie wrote:
> On Mon, Jul 17, 2023 at 19:52:01 +0000, Philip Kaludercic wrote:
> > Alan Mackenzie <acm@muc.de> writes:

[ .... ]

> > > This was achieved by adding an extra defining-symbol field to each of
> > > the three forms of function (interpreted, byte-compiled,
> > > native-compiled).  It is indended that this version of Emacs will
> > > continue to handle functions compiled without this enhancement.

> > I think the idea is nice, but there are a lot of whitespace changes in
> > your commit that make identifying the real changes a bit difficult.

> Yes.  I was instinctively correcting WS mis-alignment as I went along.
> This was a mistake, sorry.

> I've found a way to identify where these WS changes are, involving a git
> diff, and a git diff -b, taking the diff -u between these two outputs,
> then feeding that to grep '^[+-]@@'.  This identifies 10 places where the
> whitespace has changed.  I hope that's all of them, but I'll check.

> I'll go through these tomorrow morning and commit them to
> feature/named-lambdas.  This will have the advantage of making my patch
> file several hundred lines shorter.  ;-)

I've reverted a few whitespace changes (together with an unintentional
deletion of a condition-case in comp.el).

Most of the the WS changes were actually due to semantic changes, e.g. by
enclosing a block of forms in an extra (let ....).

It can help to use the -b flag in git diff (or indeed in diff itself),
e.g.

    git diff -b master..feature/named-lambdas

..

> -- 
> Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2023-07-18 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 10:14 New branch feature/named-lambdas Alan Mackenzie
2023-07-17 19:52 ` Philip Kaludercic
2023-07-17 21:37   ` Alan Mackenzie
2023-07-18 11:14     ` Alan Mackenzie [this message]
2023-07-19  8:07 ` Ihor Radchenko

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=ZLZ0CabjSHdbNJF-@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.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).