From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Navigating an enormous code base
Date: Tue, 26 Apr 2022 08:49:38 -0400 [thread overview]
Message-ID: <jwv4k2gkocd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: CAJnXXoheD8FDed-mPPPwz+WFpY+AuMmAkgyWDxmy1TU0WHOEng@mail.gmail.com
> Most often I work within a single project and want to navigate to
> files in the same project.
I think we have tools for that, such as `project-find-file` (and I'm
pretty sure there are several alternatives in third party packages).
> Less frequently I need to find a file in a sibling project.
> Unfortunately, there are ~400 siblings, though I very rarely visit
> more than 10.
I don't know of a tool for that, but I'd be interested. I never have
400 siblings (more like less than 10), but I jump between siblings very
often.
There could be several notions of "sibling":
- jump from /foo/bar/main/src/hello.c to /foo/bar/stable/src/hello.c.
- jump from /foo/bar/main/src/hello.c to /foo/bar/main/test/src/hello-tests.el.
- jump from /foo/bar/main/src/hello.c to /foo/bar/main/src/hello.h.
Not sure if we'd want to treat them together or separately (we already
have code to switch between .h and .c).
Stefan
next prev parent reply other threads:[~2022-04-26 12:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 2:31 Navigating an enormous code base John Yates
2022-04-26 6:06 ` Daniel Fleischer
2022-04-26 11:03 ` Eli Zaretskii
2022-04-26 12:53 ` John Yates
2022-04-26 14:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-04-26 12:49 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-12-14 3:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-14 17:55 ` Emanuel Berg
2022-04-27 7:59 ` Marcus Harnisch
2022-04-27 8:36 ` mrf
2022-04-27 16:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-04-27 22:59 ` John Yates
2022-04-28 0:46 ` Emanuel Berg
2022-04-28 6:42 ` Marcus Harnisch
2022-04-28 7:39 ` Leo Liu
2022-04-28 8:38 ` Marcus Harnisch
2022-04-28 10:45 ` Leo Liu
2022-04-28 14:34 ` John Yates
2022-04-28 14:45 ` Marcus Harnisch
2022-04-28 14:30 ` John Yates
2022-04-28 14:40 ` Marcus Harnisch
2022-04-28 14:50 ` John Yates
2022-04-28 16:10 ` Óscar Fuentes
2022-04-28 16:15 ` Marcus Harnisch
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=jwv4k2gkocd.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).