unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: sbaugh@catern.com
To: Eshel Yaron <me@eshelyaron.com>
Cc: 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: Sat, 30 Sep 2023 15:17:54 +0000 (UTC)	[thread overview]
Message-ID: <87zg13zo4e.fsf@catern.com> (raw)
In-Reply-To: <m1a5t3hg5l.fsf@eshelyaron.com> (Eshel Yaron's message of "Sat, 30 Sep 2023 16:47:18 +0200")

Eshel Yaron <me@eshelyaron.com> writes:
> Hi,
>
> sbaugh@catern.com writes:
>
>> Juri Linkov <juri@linkov.net> writes:
>>> Sometimes an absolute path is needed too even in project directories.
>>> Maybe it's possible to find a new prefix argument to copy
>>> a project-root-relative path like 'C-u C-u w'?
>>
>> I initially considered M-1 w, but that loses the ability to mark files
>> and then only copy one of them.  C-u C-u seems good.
>
> FWIW I think a separate command and binding would be preferable, namely
> `C-x p w`.  That'd leave `w` intact and clearly indicate the
> project-related nature of the (new) command, so it's arguably more
> intuitive than `C-u C-u w`.  We could also have that binding in
> non-Dired buffers, and have it operate on the visited file.

I don't think there's any need to avoid modifying w, so even if we added
this other C-x p w command, I would still like C-u C-u w to work.  It's
useful when navigating a project tree in dired.





  reply	other threads:[~2023-09-30 15:17 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 [this message]
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
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=87zg13zo4e.fsf@catern.com \
    --to=sbaugh@catern.com \
    --cc=66260@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=me@eshelyaron.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).