From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 9361@debbugs.gnu.org
Subject: bug#9361: 24.0.50; default value of `dired-do-chmod'
Date: Mon, 12 Sep 2011 07:45:12 -0700 [thread overview]
Message-ID: <5ADF13D8156C4D8ABED2665831AC17F2@us.oracle.com> (raw)
In-Reply-To: <87k49e7zwc.fsf@mail.jurta.org>
> 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."
Great minds think alike. ;-)
That was also one of my points: it doesn't make sense to do this when more than
one file is marked. There is no reason to privilege the "first" of the 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).
>
> Isn't what `M-.' you proposed earlier should do, i.e. pull the value
> from the buffer where the command was called?
No, I don't think so. I don't recall just what I proposed, but `M-.' in Icicles
(on which I no doubt based my proposal) pulls into the minibuffer various things
at/near point.
In this case, that is not what I propose. The user should not have to move
point to the permissions section to be able to get permissions etc.
More importantly, what I'm proposing here is a _copy_ command, which copies file
information for the file/dir of the current line. All available and pertinent
file info would be copied. Then, the individual commands (`chmod' etc.) would
have available, either (a) as default value (mentioned above) or (b) on-demand
via a different minibuffer key from `M-n', the pertinent part of the copied
info. E.g., for command `chmod', it is the file permissions part of the copied
info that is pertinent, so (only) that would be used. For command `touch', it
is the mod time of the copied file info that is pertinent, so that would be
used.
(This is akin to what is available in some editors for copying special
properties (e.g. XML attributes, face/font info, conditional text values) and
making them available via a `Paste Special' command. Whatever the last type of
special copy, the `Paste Special' pastes that to its target.)
next prev parent reply other threads:[~2011-09-12 14:45 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
2011-09-12 14:45 ` Drew Adams [this message]
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=5ADF13D8156C4D8ABED2665831AC17F2@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9361@debbugs.gnu.org \
--cc=juri@jurta.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.