From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: michael_heerdegen@web.de, 10458@debbugs.gnu.org,
monnier@IRO.UMontreal.CA
Subject: bug#10458: 24.0.92; ! in dired on a file starting with a hyphen
Date: Sun, 20 Feb 2022 16:23:55 +0200 [thread overview]
Message-ID: <83pmnhwr9g.fsf@gnu.org> (raw)
In-Reply-To: <87fsodr5mq.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 20 Feb 2022 15:10:05 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@IRO.UMontreal.CA, michael_heerdegen@web.de, 10458@debbugs.gnu.org
> Date: Sun, 20 Feb 2022 15:10:05 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It changes semantics. The list of file names passed to a command
> > doesn't necessarily mean "open each file and process it", it could
> > mean something else, like "make a list of files". So I don't think we
> > should do that.
>
> Commands like "echo" will behave differently, but I tried to imagine
> other functions where this would make a difference, and I failed. Do
> you have any examples?
Here:
find /foo/bar -name %f
I think substituting "./bar" for %f has different semantics that
"bar", doesn't it?
Basically, any scenario where "foo" doesn't mean 'the file "foo" in
the directory where the command is invoked'.
> The old behaviour would misbehave for the vast majority of commands, so
> I think it's an improvement.
In some cases, yes. I'm worried about those where it changes the
meaning, and the fact that we do this silently.
next prev parent reply other threads:[~2022-02-20 14:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 20:05 bug#10458: 24.0.92; ! in dired on a file starting with a hyphen Michael Heerdegen
2012-01-09 1:30 ` Stefan Monnier
2012-01-09 17:27 ` Glenn Morris
2012-01-09 19:39 ` Eli Zaretskii
2012-01-10 0:40 ` Richard Stallman
2012-01-09 22:40 ` Stefan Monnier
2012-01-10 7:04 ` Jan D.
2012-01-10 9:02 ` Glenn Morris
2012-01-10 14:23 ` Stefan Monnier
2012-01-10 17:11 ` Glenn Morris
2012-01-10 17:18 ` Glenn Morris
2012-01-10 20:03 ` Stefan Monnier
2012-01-10 21:45 ` Jan Djärv
2022-02-20 13:50 ` Lars Ingebrigtsen
2022-02-20 14:07 ` Eli Zaretskii
2022-02-20 14:10 ` Lars Ingebrigtsen
2022-02-20 14:23 ` Eli Zaretskii [this message]
2022-02-20 14:31 ` Lars Ingebrigtsen
2022-02-20 14:40 ` Eli Zaretskii
2022-02-21 13:46 ` Lars Ingebrigtsen
2022-02-20 15:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 13:49 ` Lars Ingebrigtsen
2022-02-22 1:32 ` Michael Heerdegen
2022-02-22 1:33 ` Lars Ingebrigtsen
2022-02-22 2:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-22 13:29 ` Lars Ingebrigtsen
2022-03-28 3:02 ` Drew Adams
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=83pmnhwr9g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10458@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
/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).