unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55778@debbugs.gnu.org, dick.r.chiang@gmail.com, monnier@iro.umontreal.ca
Subject: bug#55778: 29.0.50; [PATCH] M-. into a .gz; we've all been there.
Date: Wed, 08 Jun 2022 13:39:59 +0200	[thread overview]
Message-ID: <87tu8vbcz4.fsf@gnus.org> (raw)
In-Reply-To: <83mteo7lrr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Jun 2022 14:31:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> No?  "Alist of extensions to find given the current file's extension."
>> `find-sibling-rules' isn't about extensions.
>
> It isn't?  Then why did you show these examples:
>
>> So I've now added a new command `find-sibling-file' to Emacs 29.  This
>> setting does what the latter:
>> 
>> (setq find-sibling-rules
>>       '(("\\(/usr/share/emacs.*/\\(lisp/.*.el\\).gz\\)"
>> 	 "/home/larsi/src/emacs/trunk/\\2\\'")))

That's not about extensions, but finding a related file in a different
directory.

> Anyway, I'm not saying that find-file.el can support everything you
> wanted to support OOTB.  But it can support most of it, and it can be
> extended to support the rest.  So it sounds strange to me to come up
> with an entirely new feature, implemented from scratch and with an
> incompatible API, when these two have such a significant functionality
> overlap.

I understand your point, but I don't feel there's much to be gained
trying to merge these two things that have somewhat different use cases.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-08 11:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  6:27 bug#55778: 29.0.50; [PATCH] M-. into a .gz; we've all been there dick.r.chiang
2022-06-03 10:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 10:52 ` Lars Ingebrigtsen
2022-06-05 13:49   ` Lars Ingebrigtsen
2022-06-05 13:57     ` Eli Zaretskii
2022-06-05 14:02       ` Lars Ingebrigtsen
2022-06-05 14:15         ` Eli Zaretskii
2022-06-06 12:25           ` Lars Ingebrigtsen
2022-06-06 12:51             ` Eli Zaretskii
2022-06-07  9:13               ` Lars Ingebrigtsen
2022-06-07 11:31                 ` Eli Zaretskii
2022-06-08 11:39                   ` Lars Ingebrigtsen [this message]
2022-06-03 11:41 ` Eli Zaretskii
2022-06-04 16:52   ` dick
2022-06-04 17:29     ` Eli Zaretskii
2022-06-03 13:24 ` Dmitry Gutov
2022-06-03 13:41   ` Eli Zaretskii
2022-06-14 12:42 ` Lars Ingebrigtsen

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=87tu8vbcz4.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55778@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=eliz@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.
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).