From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 9361@debbugs.gnu.org
Subject: bug#9361: 24.0.50; default value of `dired-do-chmod'
Date: Mon, 12 Sep 2011 14:39:47 +0300 [thread overview]
Message-ID: <87k49e7zwc.fsf@mail.jurta.org> (raw)
In-Reply-To: <1BDADB23B4434E0C9330F1B010F1E1CE@us.oracle.com> (Drew Adams's message of "Sun, 11 Sep 2011 08:00:58 -0700")
> 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.
There was followup, but off-list unfortunately. I replied to RMS with:
"The values are file attributes of all marked files (modes for M,
owners for O, groups or G, timestamps for T). But now I see that
these values are not very useful, so I withdraw my proposal."
And RMS encouraged to do this for just one marked file:
"When there is just one marked file, the feature could indeed be useful.
So I suggest you limit it to that case, and document clearly where the
default comes from, so that people will know how they can make use
of the feature."
> 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).
Isn't what `M-.' you proposed earlier should do, i.e. pull the value
from the buffer where the command was called?
next prev parent reply other threads:[~2011-09-12 11:39 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
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 [this message]
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
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=87k49e7zwc.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9361@debbugs.gnu.org \
--cc=drew.adams@oracle.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).