From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: michael_heerdegen@web.de, 10458@debbugs.gnu.org
Subject: bug#10458: 24.0.92; ! in dired on a file starting with a hyphen
Date: Mon, 21 Feb 2022 21:51:43 -0500 [thread overview]
Message-ID: <jwvpmnfiplk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ley4l48d.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 21 Feb 2022 14:49:06 +0100")
>> The problem with that is that it's hackish and ad-hoc. It will
>> sometimes do the right thing, but other times it' not what's expected
>> and users will find it odd.
>
> Statistically speaking, it'll work on more cases than `!' used to,
> though. I'm pretty sure. And I think it's fine for a command like `!'
> to try to DWIM.
I was thinking of making it less-DWIMish and leave it in control of
the user. IOW, rather than try to magically "do the right thing" for
files starting with `-`, allow the users to request explicitly absolute
file names (maybe with a prefix command or something like that) when
*they* see it's needed.
It won't fix the user's mistakes, but it will give a simpler semantics
on which powerusers can more easily rely.
Stefan
next prev parent reply other threads:[~2022-02-22 2:51 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
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 [this message]
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=jwvpmnfiplk.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@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).