From: Gregory Heytings via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Exploring a code base?
Date: Sat, 07 Nov 2020 15:32:51 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2011071621480453.15736@sdf.lonestar.org> (raw)
In-Reply-To: <837dqx6x65.fsf@gnu.org>
>
> As for discovering that a problem includes more places and symbols than
> one originally envisioned: one can maintain a flat list of
> functions/modules/whatever to look into, and add to that as more stuff
> is being found. You can do it in Org or even in a simple text buffer.
> If there's really a need to maintain some structure, one can use Org's
> level headings to that end.
>
Yes, this is almost word for word what Yuri explained in his first mail,
and Stefan in his reply. Yuri says that doing this is "tedious", Stefan
that it is "not satisfactory". So the question is: could this not be
automated with a kind of stack or list of searches, in which one could
navigate, instead of using a separate flat or structured text file?
next prev parent reply other threads:[~2020-11-07 15:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 11:38 Exploring a code base? Yuri Khan
2020-10-27 11:58 ` Christopher Dimech
2020-10-27 14:15 ` Stefan Monnier
2020-10-27 15:55 ` Drew Adams
2020-10-27 20:56 ` Dmitry Gutov
2020-11-07 13:26 ` Yuri Khan
2020-11-07 13:56 ` Eli Zaretskii
2020-11-07 14:33 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-11-07 14:47 ` Eli Zaretskii
2020-11-07 15:32 ` Gregory Heytings via Users list for the GNU Emacs text editor [this message]
2020-11-07 15:52 ` Stefan Monnier
2020-11-07 15:58 ` Eli Zaretskii
2020-11-07 17:24 ` Eric Abrahamsen
2020-11-07 19:23 ` Dmitry Gutov
2020-11-07 19:40 ` Dmitry Gutov
2020-10-27 20:59 ` Perry Smith
2020-10-27 22:53 ` Daniel Martín
2020-10-27 23:15 ` Stefan Monnier
2020-10-28 0:59 ` Skip Montanaro
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=alpine.NEB.2.22.394.2011071621480453.15736@sdf.lonestar.org \
--to=help-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=ghe@sdf.org \
/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.