From: Dmitry Gutov <dmitry@gutov.dev>
To: Spencer Baugh <sbaugh@janestreet.com>, 73044-done@debbugs.gnu.org
Subject: bug#73044: [PATCH] Add project-find-file-in-root
Date: Fri, 6 Sep 2024 19:20:16 +0300 [thread overview]
Message-ID: <a51a05f1-4dd4-4fbc-8fa4-8355c6f1e97e@gutov.dev> (raw)
In-Reply-To: <iery14619o5.fsf@janestreet.com>
Version: 31.1
Hi Spencer,
On 05/09/2024 17:01, Spencer Baugh via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> Several users have asked me for a command which is just
> find-file, but starting from the project root. In large
> projects, where project-files is expensive, this will have
> substantially better performance than project-find-file.
>
> Also, it allows opening files which aren't included in
> project-files without paying the further cost of running
> project--files-in-directory (which is what happens when passing
> INCLUDE-ALL=t to project-find-file).
>
> Also, it may help with user confusion about why
> project-find-file doesn't behave like find-file. (which I've
> encountered a few times)
>
> This command is equivalent to C-x p o C-x C-f, but it's nice to
> be able to bind it to a specific key.
>
> Overall, this is easy enough to provide, so let's just do that.
Makes sense, thanks, pushed to master (adding the 'interactive' form and
a NEWS entry).
The name is a little verbose - if anybody has a better idea later,
they're welcome to suggest it, there is some time to do a change.
next prev parent reply other threads:[~2024-09-06 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 14:01 bug#73044: [PATCH] Add project-find-file-in-root Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-06 16:20 ` Dmitry Gutov [this message]
2024-09-06 17:44 ` Eli Zaretskii
2024-09-06 20:05 ` Dmitry Gutov
2024-09-07 6:10 ` Eli Zaretskii
2024-09-08 2:14 ` Dmitry Gutov
2024-09-15 18:14 ` Sean Whitton
2024-09-16 23:12 ` Dmitry Gutov
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=a51a05f1-4dd4-4fbc-8fa4-8355c6f1e97e@gutov.dev \
--to=dmitry@gutov.dev \
--cc=73044-done@debbugs.gnu.org \
--cc=sbaugh@janestreet.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).