emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#30285: closed (dired-do-chmod vs. top line of dire


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#30285: closed (dired-do-chmod vs. top line of dired)
Date: Tue, 06 Feb 2018 21:33:02 +0000

Your message dated Tue, 06 Feb 2018 23:32:21 +0200
with message-id <address@hidden>
and subject line Re: bug#30285: dired-do-chmod vs. top line of dired
has caused the debbugs.gnu.org bug report #30285,
regarding dired-do-chmod vs. top line of dired
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30285: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30285
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: dired-do-chmod vs. top line of dired Date: Mon, 29 Jan 2018 20:32:51 +0800
M runs the command dired-do-chmod.
If used on the very top line of dired
(the directory name,) it says:
"Change mode of * [0 files] to: "
which doesn't make a lot of sense.
emacs-version "25.2.2"

Same problem if used on the second line, (total...).

(Why doesn't it just complain "can't operate on" like it does for the
third line, ".".)



--- End Message ---
--- Begin Message --- Subject: Re: bug#30285: dired-do-chmod vs. top line of dired Date: Tue, 06 Feb 2018 23:32:21 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu)
> Wouldn't this
>
> -  (let* ((files (dired-get-marked-files t arg))
> +  (let* ((files (or (dired-get-marked-files t arg)
> +                    (user-error "No files specified")))
>
> call for an extra argument to 'dired-get-marked-files' to emit the
> user error right there?  If it's TRT in your cases, it might give
> coders a heads-up that it's TRT in their cases as well.

This is now pushed to master and closed.


--- End Message ---

reply via email to

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