From: Lars Ingebrigtsen <larsi@gnus.org>
To: Damien Cassou <damien@cassou.me>
Cc: Eli Zaretskii <eliz@gnu.org>, 58071@debbugs.gnu.org
Subject: bug#58071: 28.2; [PATCH] jumprel: A tool to find/create related files
Date: Thu, 29 Sep 2022 12:46:24 +0200 [thread overview]
Message-ID: <87ill6ihkv.fsf@gnus.org> (raw)
In-Reply-To: <874jwr9u6c.fsf@cassou.me> (Damien Cassou's message of "Wed, 28 Sep 2022 21:26:51 +0200")
Damien Cassou <damien@cassou.me> writes:
> I'm not sure I understand what you mean. I agree that there is no point
> in having 10 many different completion frameworks in Emacs core (even
> though we might be close to this number already 😊).
>
> Similarly, I wouldn't like to have 3 find-related-files packages. But I
> think that, contrary to completion frameworks, these 3 packages provide
> the same feature: namely "a command to find file(s) related to the
> current one". Said differently, the user-visible behavior is the
> same. As soon as the setup is done, there shouldn't any difference
> between `find-sibling-file' and `jumprel'.
The similarity between completion frameworks and "jumping to files" is
that people have different needs. Some would prefer something that
guesses for you, while others prefer to make the rules explicit.
next prev parent reply other threads:[~2022-09-29 10:46 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ill6ihkv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58071@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=eliz@gnu.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.