From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 30285@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>,
jidanni@jidanni.org
Subject: bug#30285: dired-do-chmod vs. top line of dired
Date: Thu, 01 Feb 2018 23:35:50 +0200 [thread overview]
Message-ID: <871si475qh.fsf@mail.linkov.net> (raw)
In-Reply-To: <5620cf82-9402-4895-bdd1-fdf5401c8172@default> (Drew Adams's message of "Thu, 1 Feb 2018 12:50:16 -0800 (PST)")
>> Since `dired-mark' from the top line followed by the command in question
>> is not obvious for users, we could provide a hint in the error message,
>> i.e. mention the availability of ‘m’ on the top line with such message:
>> “You can type `m' here to mark all files for this operation”.
>
> Not sure how helpful or necessary that is. It's liable to
> not be helpful (that use case needs no special advertising).
> And it might even confuse things. I think it just gets in
> the way of the message, which is, "You are not on a file line."
This message is absolutely wrong, it doesn't describe the state that causes
the error message. It has a bigger scope than just file lines, it works
with marked files, etc. So more correct message would be like this:
“No files selected.”
Oh, and I discovered that the current state is much worse than I thought:
1. load dired-x
2. type ‘M-<’ to go to the first line
3. type ‘!’ (dired-do-shell-command)
“Wrong type argument: stringp, nil”
next prev parent reply other threads:[~2018-02-01 21:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 12:32 bug#30285: dired-do-chmod vs. top line of dired 積丹尼 Dan Jacobson
2018-01-29 15:14 ` Tino Calancha
2018-01-29 16:05 ` Eli Zaretskii
2018-01-29 23:21 ` Tino Calancha
2018-01-29 23:42 ` Drew Adams
2018-01-30 3:53 ` Tino Calancha
2018-01-30 4:43 ` Drew Adams
2018-01-30 15:15 ` Drew Adams
2018-01-31 9:49 ` Tino Calancha
2018-01-31 19:04 ` Drew Adams
2018-01-31 21:35 ` Juri Linkov
2018-01-31 23:20 ` Drew Adams
2018-02-01 8:16 ` Tino Calancha
2018-02-01 9:17 ` Tino Calancha
2018-02-01 16:10 ` Drew Adams
2018-02-04 23:12 ` Tino Calancha
2018-02-05 16:45 ` Drew Adams
2018-02-01 20:07 ` Juri Linkov
2018-02-01 20:50 ` Drew Adams
2018-02-01 21:35 ` Juri Linkov [this message]
2018-02-01 22:23 ` Drew Adams
2018-02-03 22:23 ` Juri Linkov
2018-02-04 10:02 ` martin rudalics
2018-02-04 21:44 ` Juri Linkov
2018-02-06 21:32 ` Juri Linkov
2018-02-04 23:08 ` Tino Calancha
2018-02-05 21:01 ` Juri Linkov
2018-02-05 21:52 ` Drew Adams
2018-01-29 15:24 ` 積丹尼 Dan Jacobson
2018-01-29 23:14 ` Tino Calancha
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=871si475qh.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=30285@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jidanni@jidanni.org \
--cc=tino.calancha@gmail.com \
/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).