GNU bug report logs - #16056
dired-do-chmod vs. dired-get-filename message

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16056 in the body.
You can then email your comments to 16056 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: dired-do-chmod vs. dired-get-filename message
Date: Thu, 05 Dec 2013 09:16:03 +0800

M runs the command dired-do-chmod
which works on ., despite
dired-get-filename: Cannot operate on `.' or `..'
annoying messages.

Message #8 received at 16056 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: jidanni <at> jidanni.org
Cc: 16056 <at> debbugs.gnu.org
Subject: Re: bug#16056: dired-do-chmod vs. dired-get-filename message
Date: Wed, 14 Aug 2019 19:28:10 -0700

jidanni <at> jidanni.org writes:

> M runs the command dired-do-chmod
> which works on ., despite
> dired-get-filename: Cannot operate on `.' or `..'
> annoying messages.

(I'm going through old bug reports that have unfortunately gotten no
responses yet.)

I tried doing `M' on a "." file in dired, and I didn't get any
"Cannot operate on `.' or `..'" messages, so this looks like it's been
fixed in the intervening years, and I'm closing this bug report.  If
you're still seeing this, please reopen and provide a full recipe for
how to reproduce the bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.