From: Felician Nemeth <felician.nemeth@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57325@debbugs.gnu.org
Subject: bug#57325: 27.1; functions in ff-other-file-alist
Date: Tue, 30 Aug 2022 10:46:22 +0200 [thread overview]
Message-ID: <87pmgiqftt.fsf@betli.tmit.bme.hu> (raw)
In-Reply-To: <83edwzvvtg.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Aug 2022 19:49:47 +0300")
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> >> Also, when the function returns an absolute file name, then the
>> >> returned file should be already opened, otherwise ff-find-other-file
>> >> cannot find it.
>> >
>> > Hmm... not sure how this is relevant. The function should return a
>> > list of extensions, not a file name. What am I missing?
>>
>> In my case, the related file of foo.toml is bar.json. From an extension
>> it is not possible to guess whether the related file is bar.json or
>> baz.json. find-file.el of Emacs 27.1 has this in the Commentary
>> section:
>>
>> ;; These functions must return a list consisting of the possible names of the
>> ;; corresponding file, with or without path.
>>
>> That's why I thought my function could return an absolute file name.
>
> If the returned list includes file names with leading directories,
> find-file.el strips the leading directories and uses the basename to
> match against.
I think that not how it works. Even if the attached file is in a
directory that contains a file named "hosts", when I
1. emacs -Q test.el
2. y
3. M-x eval-buffer RET
4. M-x ff-find-other-file RET
Emacs is going to switch to the buffer containing /etc/hosts.
> Another thing to clarify in the docs?
Playing with the implementation, I think that these functions shouldn't
return extensions. They should return file names.
[-- Attachment #2: test.el --]
[-- Type: application/emacs-lisp, Size: 175 bytes --]
next prev parent reply other threads:[~2022-08-30 8:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 18:34 bug#57325: 27.1; functions in ff-other-file-alist Felician Nemeth
2022-08-21 18:55 ` Eli Zaretskii
2022-08-21 19:37 ` Felician Nemeth
2022-08-22 11:44 ` Eli Zaretskii
2022-08-25 8:14 ` Eli Zaretskii
2022-08-29 11:57 ` Felician Nemeth
2022-08-29 14:04 ` Eli Zaretskii
2022-08-29 14:27 ` Felician Nemeth
2022-08-29 16:49 ` Eli Zaretskii
2022-08-30 8:46 ` Felician Nemeth [this message]
2022-08-30 12:43 ` Eli Zaretskii
2022-08-30 13:48 ` Felician Nemeth
2022-08-30 16:10 ` Eli Zaretskii
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=87pmgiqftt.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=57325@debbugs.gnu.org \
--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 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).