From: sbaugh@catern.com
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Eli Zaretskii <eliz@gnu.org>,
66260@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#66260: 29.0.92; project.el should support copying a file path relative to the project root
Date: Tue, 03 Oct 2023 20:49:33 +0000 (UTC) [thread overview]
Message-ID: <87jzs3zb1f.fsf@catern.com> (raw)
In-Reply-To: <6a454175-c709-3473-fdb4-e4be39e2d8fe@gutov.dev> (Dmitry Gutov's message of "Mon, 2 Oct 2023 14:46:43 +0300")
Dmitry Gutov <dmitry@gutov.dev> writes:
> On 02/10/2023 09:53, Juri Linkov wrote:
>>>> 'C-x p w' does make sense as such, but it would be unfortunate if we
>>>> find a more important command later which fits the 'w' mnemonics. Maybe
>>>> 'C-x p W' would be a more conservative choice.
>>> Or even "C-x p C-w".
>> Or 'C-x p C-c' like 'c' in Info-mode-map for Info-copy-current-node-name.
>
> That one was probably made from the CUA user's standpoint.
>
> I sympathize, but even Info-mode-map has a 'w' binding (thanks to you,
> looks like).
>
> So C-w or M-w seem like a better choice for the default bindings.
I don't think C-x p w is quite necessary. But even if it was, I think
there's a good other candidate for what it should do: copy the project
root. That would also be pretty useful.
For example, I often move a patch between two projects by first
rendering it in one project (with C-x v D), entering M-x cd
other/project/root in the *vc-diff* buffer, and then applying the diff.
If there was a quick way to get other/project/root, it would speed this
up.
Sometimes I also run shell commands which need the project root.
I can always do C-x p D then copy the file name of that buffer, but
that's about as painful as C-x C-j C-u C-u w, so if C-x C-j C-u C-u w is
too cumbersome then it seems to me that so is C-x p D and copy.
next prev parent reply other threads:[~2023-10-03 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 23:26 bug#66260: 29.0.92; project.el should support copying a file path relative to the project root sbaugh
2023-09-29 6:57 ` Juri Linkov
2023-09-30 13:50 ` sbaugh
2023-09-30 14:47 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 15:17 ` sbaugh
2023-10-01 22:44 ` Dmitry Gutov
2023-10-02 5:57 ` Eli Zaretskii
2023-10-02 6:53 ` Juri Linkov
2023-10-02 11:46 ` Dmitry Gutov
2023-10-03 20:49 ` sbaugh [this message]
2023-10-03 21:17 ` Dmitry Gutov
2023-10-02 11:13 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 13:13 ` sbaugh
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=87jzs3zb1f.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=66260@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).