Subject: bug#75910: 31; Deprecate minibuffer-completing-file-name

From: Drew Adams <[email-masked]>
Date: Thu, 30 Jan 2025 18:00:04 +0000

> >> This is almost never correct nor desired,
> >> as you acknowledge yourself below.
> >
> > You're exaggerating.  "Usually" and "often" are
> > not the same as "almost always".
> 
> No, I really mean almost always. 

Sure you do.  But what you also said was that
_I_ said _I_ mean that too.  And that's _not_
what I said.

> One does not want some variable setting
> which is meant to affect a certain outer completion session to also
> affect arbitrary other nested completion sessions, which are started by
> the user.

"One" -> you.

> Right now, the let-binding of minibuffer-completing-file-name around
> completing-read means that all inner completion sessions also complete
> file names. This is simply not correct.

No, it doesn't - it shouldn't.  It means that
they're made aware of the fact that a file-name
completion is in progress.  They occur _during_
that file-name completion.  It's just a variable.
They don't need to, themselves, complete a file
name.