From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: 58071@debbugs.gnu.org
Subject: bug#58071: 28.2; [PATCH] jumprel: A tool to find/create related files
Date: Mon, 26 Sep 2022 10:42:15 +0300 [thread overview]
Message-ID: <83k05qlgyw.fsf@gnu.org> (raw)
In-Reply-To: <878rm7wvib.fsf@cassou.me> (message from Damien Cassou on Sun, 25 Sep 2022 13:20:28 +0200)
> From: Damien Cassou <damien@cassou.me>
> Date: Sun, 25 Sep 2022 13:20:28 +0200
>
> Please find attached jumprel, a tool to find/create related files. This
> tool has been described (and compared with `find-file.el' and
> `find-sibling-file') in emacs-devel's thread "Comparison of tools to
> search for related files".
Thanks. A few high-level comments I have are:
. "jumprel" is not the best name, IMO; something like "related-files"
would be better
. what you call "recipes", i.e. descriptors of how to generate the
name of related files from a given file name, should be documented
in a single doc string, and the other places that use recipes
should reference the symbol whose doc string documents them
(currently, it looks like the documentation is scattered all over
the code and comments, and mainly as examples; there's no single
exhaustive list with descriptions)
. I find no documentation of how to describe alternatives -- several
alternative file names produced from a single original file name
. I wonder whether "recipes" like these are a convenient method of
customizing this facility: do people really find it easy to write
"ordered" property lists for this purpose?
next prev parent reply other threads:[~2022-09-26 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 11:20 bug#58071: 28.2; [PATCH] jumprel: A tool to find/create related files Damien Cassou
2022-09-26 7:42 ` Eli Zaretskii [this message]
2022-09-28 19:26 ` Damien Cassou
2022-09-29 8:54 ` Eli Zaretskii
2022-09-30 8:43 ` Damien Cassou
2022-09-30 10:38 ` Eli Zaretskii
2022-09-29 10:46 ` Lars Ingebrigtsen
2022-09-30 8:44 ` Damien Cassou
2022-10-06 6:09 ` Damien Cassou
2022-09-26 11:05 ` Lars Ingebrigtsen
2022-09-26 13:37 ` Stefan Kangas
2022-09-27 11:34 ` Lars Ingebrigtsen
2022-10-28 22:08 ` hugo
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=83k05qlgyw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58071@debbugs.gnu.org \
--cc=damien@cassou.me \
/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).