Subject: bug#30285: closed (Re: bug#30285: dired-do-chmod vs. top line of dired)

From: [email-masked] (GNU bug Tracking System)
Date: Tue, 06 Feb 2018 21:33:02 +0000

Your bug report

#30285: dired-do-chmod vs. top line of dired

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
30285: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30285
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#30285: dired-do-chmod vs. top line of dired
From: Juri Linkov <[email-masked]>
To: martin rudalics <[email-masked]>
Cc: [email-masked], [email-masked], Drew Adams <[email-masked]>, Tino Calancha <[email-masked]>
Date: Tue, 06 Feb 2018 23:32:21 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

> 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.

Subject: dired-do-chmod vs. top line of dired
From: 積丹尼 Dan Jacobson <[email-masked]>
To: [email-masked]
Date: Mon, 29 Jan 2018 20:32:51 +0800
List-Id: <debbugs-submit.debbugs.gnu.org>

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, ".".)