[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: master 82ccc3a: ; Mention the previous change in NEWS

From: Eli Zaretskii
Subject: Re: master 82ccc3a: ; Mention the previous change in NEWS
Date: Tue, 08 Jun 2021 18:44:58 +0300

> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 8 Jun 2021 18:21:19 +0300
> Customizing grep-find-template to include a specific directory sounds 
> stupid: that would break rgrep and other commands that use it.
> So I probably don't understand what you meant.

What I meant was that <D> is there, and it could be used to mean
something other than ".".  But I don't think it's worth our while to
continue developing this sub-thread, it is not important enough for
the issue at hand.

> >>>> xref-matches-in-directory has no known callers anymore, but any
> >>>> third-party code should see the IGNORES honored better with those old
> >>>> versions of 'find'.
> >>>
> >>> So we could say that any command which uses xref-matches-in-directory
> >>> is affected.
> >>
> >> Is that better than saying that the variable changed? Possibly affecting
> >> any code that uses it is an obvious implication.
> > 
> > How about saying both?
> No objection from me.
> >> We can say that about xref-matches-in-directory, noting that the change
> >> is likely to only be noticeable with old versions of 'find'.
> > 
> > That'd be good, yes.
> > 
> >> Which apparently includes macOS systems, but I'm not sure which
> >> ones, and whether using "Homebrew" or not matters for this case.
> > 
> > Maybe also some *BSD?  We could mention macOS, or we could say
> > something like "non-GNU Find".
> Some -- maybe.
> But I tried one or two recent FreeBSD releases in a VM, and they didn't 
> have that problem.

So would you like me to propose the wording, or will you do it?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]