From: "Drew Adams" <drew.adams@oracle.com>
To: <10624@debbugs.gnu.org>
Subject: bug#10624: 24.0.92; default value of `dired-do-ch*'
Date: Fri, 27 Jan 2012 08:23:19 -0800 [thread overview]
Message-ID: <60BBA8177B8C4157BBB5426B2F6A8204@us.oracle.com> (raw)
In-Reply-To: <0F10A2A4C6E541469381BA91CB8AEEB3@us.oracle.com>
Let me include this bit also from bug #9361. It offers a bit more in the way of
suggestion for the requested enhancement.
> 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:[~2012-01-27 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 15:35 bug#10624: 24.0.92; default value of `dired-do-ch*' Drew Adams
2012-01-27 16:23 ` Drew Adams [this message]
2012-09-14 23:47 ` Juri Linkov
2012-09-15 0:37 ` Drew Adams
2012-09-15 22:50 ` Juri Linkov
2012-09-16 4:47 ` Drew Adams
2012-09-16 23:48 ` Juri Linkov
2012-09-17 0:39 ` Drew Adams
2012-09-18 23:22 ` Juri Linkov
2012-09-15 22:54 ` Juri Linkov
2012-09-16 4:47 ` Drew Adams
2012-09-16 23:45 ` bug#10624: Dired-marking all files in the region Juri Linkov
2012-11-22 9:49 ` Juri Linkov
2012-11-22 15:27 ` Drew Adams
2012-11-23 7:51 ` Juri Linkov
2012-11-23 17:12 ` Drew Adams
2012-11-25 9:16 ` Juri Linkov
2012-11-25 15:49 ` Drew Adams
2012-11-25 16:12 ` Juri Linkov
2012-11-25 17:02 ` Drew Adams
2012-11-22 15:40 ` Stefan Monnier
2012-11-23 7:59 ` Juri Linkov
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=60BBA8177B8C4157BBB5426B2F6A8204@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10624@debbugs.gnu.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 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).