From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>,
"'Juri Linkov'" <juri@jurta.org>
Cc: 9361@debbugs.gnu.org
Subject: bug#9361: 24.0.50; default value of `dired-do-chmod'
Date: Sun, 11 Sep 2011 08:00:58 -0700 [thread overview]
Message-ID: <1BDADB23B4434E0C9330F1B010F1E1CE@us.oracle.com> (raw)
In-Reply-To: <m31uvn6cm4.fsf@stories.gnus.org>
> I agree, so I'm closing this report.
I disagree, so I'm reopening it.
In the _very_ long thread cited by Juri, there was only one comment on this
proposal for a default value for `dired-do-chmod' etc. It was from RMS:
"I am not sure that this is very useful. What are the values
you think of providing?"
There was no followup, and this was never approved.
Juri makes the argument that this is handy because it lets you easily copy the
permissions from "the marked file" and reuse them elsewhere.
That is no argument when more than one file is marked. In fact it might be an
argument for using as default the file of the current (cursor) line. It makes
absolutely no sense to privilege the first of a non-singleton set of marked
files.
In reality, it is an argument for having a separate command to copy the settings
(all of them) from the current line and then having, as default value for each
of the `*ch*' commands, the value taken from that copied setting. And this
would apply across Dired buffers, giving you an easy way to apply a particular
set of values (settings). It could perhaps also apply to other Dired commands,
such as `touch' (dunno).
The point is that if we are going to copy settings from a particular file in
order to make them available for, essentially, pasting operations to other
files, then the target file being copied from should be clear. The copy
operation should be an explicit user choice, not something implicit, based only
on the first marked file (why not the last? or the 23rd?).
next prev parent reply other threads:[~2011-09-11 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 16:10 bug#9361: 24.0.50; default value of `dired-do-chmod' Drew Adams
2011-08-24 18:45 ` Juri Linkov
2011-09-11 2:23 ` Lars Magne Ingebrigtsen
2011-09-11 15:00 ` Drew Adams [this message]
2011-09-11 21:41 ` Chong Yidong
2011-09-12 11:49 ` Juri Linkov
2011-09-12 20:47 ` Chong Yidong
2011-09-14 11:20 ` Juri Linkov
2011-09-14 15:07 ` Chong Yidong
2011-09-14 15:54 ` Juri Linkov
2011-09-12 11:39 ` Juri Linkov
2011-09-12 14:45 ` Drew Adams
2012-01-26 16:27 ` Drew Adams
2012-01-27 1:38 ` Juri Linkov
2012-01-27 3:04 ` Drew Adams
2012-01-27 7:24 ` Chong Yidong
2012-01-27 12:09 ` Juri Linkov
2012-01-27 16:58 ` Drew Adams
2012-01-27 15:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1BDADB23B4434E0C9330F1B010F1E1CE@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9361@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.