From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Ivan Sokolov <ivan-p-sokolov@ya.ru>
Cc: 64531@debbugs.gnu.org
Subject: bug#64531: [PATCH v3] Add new commands for copying VC filenames
Date: Fri, 20 Oct 2023 02:39:24 +0300 [thread overview]
Message-ID: <e66c7b3c-dab2-fffb-f0b7-8670ba9d467a@yandex.ru> (raw)
In-Reply-To: <83o7ig51ej.fsf@gnu.org>
On 05/09/2023 14:01, Eli Zaretskii wrote:
>> From: Ivan Sokolov<ivan-p-sokolov@ya.ru>
>> Cc: Eli Zaretskii<eliz@gnu.org>, Dmitry Gutov<dgutov@yandex.ru>
>> Date: Mon, 04 Sep 2023 23:08:02 +0300
>>
>> I tried to write documentation for the previous version of the command
>> and came to the conclusion that I crammed too much functionality into
>> it. So I divided the DWIM command into command for copying name at
>> point (bound to w) and command for copying marked files (bound to * w).
>>
>> I also added new command for copying VC related filenames from
>> everywhere. An appropriate binding would be C-x v w, but I am not sure
>> if I should use a top-level binding for such an insignificant command.
>>
>> Quoting and prefix arguments now copy `dired-copy-filename-as-kill'.
> Thanks, a few minor comments about the documentation parts:
Thank for the doc changes review.
The code looks good, FWIW.
prev parent reply other threads:[~2023-10-19 23:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 7:51 bug#64531: [PATCH] Add new command vc-dir-copy-filename-as-kill Ivan Sokolov
2023-07-08 9:25 ` Eli Zaretskii
2023-08-08 13:44 ` bug#64531: [PATCH v2] " Ivan Sokolov
2023-08-08 13:56 ` Eli Zaretskii
2023-08-19 8:06 ` Eli Zaretskii
2023-08-19 23:12 ` Ivan Sokolov
2023-08-20 6:20 ` Eli Zaretskii
2023-08-19 23:33 ` Dmitry Gutov
2023-08-20 6:26 ` Eli Zaretskii
2023-08-20 10:26 ` Dmitry Gutov
2023-09-04 20:08 ` bug#64531: [PATCH v3] Add new commands for copying VC filenames Ivan Sokolov
2023-09-05 11:01 ` Eli Zaretskii
2023-10-19 23:39 ` Dmitry Gutov [this message]
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=e66c7b3c-dab2-fffb-f0b7-8670ba9d467a@yandex.ru \
--to=dgutov@yandex.ru \
--cc=64531@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ivan-p-sokolov@ya.ru \
/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.