From: Sebastian Poeplau <sebastian.poeplau@mailbox.org>
To: Felician Nemeth <felician.nemeth@gmail.com>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
Subject: Re: eglot's interface for major modes
Date: Thu, 13 Apr 2023 21:24:39 +0200 [thread overview]
Message-ID: <871qknwplo.fsf@mailbox.org> (raw)
In-Reply-To: <87leiyy0na.fsf@betli.tmit.bme.hu>
>> I may be mistaken, but my understanding of ff-other-file-alist is that
>> it needs to be set to a mapping between file extensions of specification
>> and implementation files; whatever the value, ff-find-other-file will
>> use the algorithm in find-file.el.
>
> Even the algorithm can be redefined. The latest version of the
> documentation of variable ff-other-file-alist explains the details.
Interesting! I checked the doc string in Emacs 28 before writing my
earlier message; it seems that a lot has changed since then :)
> Eglot-x contains a possibly overly complicated example that also
> delegates the ff-other-file functionality to LSP servers.
> <https://github.com/nemethf/eglot-x>
>
> But it's basically
>
> (setq-local ff-other-file-alist '(("*.ext ext-mode--ff-other-file)))
That would indeed be a good fit! I'll have a look.
next prev parent reply other threads:[~2023-04-13 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:20 eglot's interface for major modes Sebastian Poeplau
2023-04-07 21:26 ` Stephen Leake
2023-04-08 9:13 ` Felician Nemeth
2023-04-08 9:37 ` Sebastian Poeplau
2023-04-11 14:05 ` Felician Nemeth
2023-04-13 19:24 ` Sebastian Poeplau [this message]
2023-04-13 16:22 ` João Távora
2023-04-13 17:43 ` Felician Nemeth
2023-04-13 19:36 ` Sebastian Poeplau
2023-04-08 9:26 ` Sebastian Poeplau
2023-04-08 10:30 ` Stephen Leake
2023-04-08 10:53 ` Sebastian Poeplau
2023-04-12 23:06 ` Stephen Leake
2023-04-13 19:23 ` Sebastian Poeplau
2023-04-15 16:38 ` Stephen Leake
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=871qknwplo.fsf@mailbox.org \
--to=sebastian.poeplau@mailbox.org \
--cc=emacs-devel@gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=stephen_leake@stephe-leake.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 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).