From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 74467@debbugs.gnu.org, yantar92@posteo.net, binarin@binarin.info
Subject: bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional
Date: Sun, 05 Jan 2025 21:11:19 +0200 [thread overview]
Message-ID: <86ed1h6ppk.fsf@gnu.org> (raw)
In-Reply-To: <87sepxt953.fsf@> (message from Björn Bidar on Sun, 05 Jan 2025 20:20:40 +0200)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: yantar92@posteo.net, 74467@debbugs.gnu.org, binarin@binarin.info
> Date: Sun, 05 Jan 2025 20:20:40 +0200
>
> Do I understand correctly that when Emacs starts it tries to find the
> file-handler in C but the call to the handler is done in Lisp code?
AFAIR, file-handlers are looked for on both C and Lisp level. What
matters is the level on which the operation is implemented. If it's
implemented in C, we must look for the handler in C, otherwise we can
look for it in Lisp. find-file-name-handler is a primitive
implemented in C, but you can call it both from C and from Lisp.
prev parent reply other threads:[~2025-01-05 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 18:53 bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional Alexey Lebedeff via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 13:12 ` Eli Zaretskii
2024-11-23 19:58 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 12:17 ` Eli Zaretskii
2024-12-16 19:34 ` Ihor Radchenko
2024-12-16 20:01 ` Eli Zaretskii
2024-12-16 21:07 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87o71bgwvl.fsf@>
2024-12-17 12:15 ` Eli Zaretskii
2024-12-17 13:00 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-28 11:37 ` Eli Zaretskii
2025-01-02 20:02 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfk9q91e.fsf@>
2025-01-04 13:18 ` Eli Zaretskii
2025-01-04 22:07 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <877c7aw7va.fsf@>
2025-01-05 6:39 ` Eli Zaretskii
2025-01-05 8:55 ` Ihor Radchenko
2025-01-05 18:13 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87wmf9t9hm.fsf@>
2025-01-05 18:36 ` Ihor Radchenko
2025-01-05 21:31 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87cyh1t0ag.fsf@>
2025-01-06 18:44 ` Ihor Radchenko
2025-01-07 8:05 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 18:20 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87sepxt953.fsf@>
2025-01-05 19:11 ` Eli Zaretskii [this message]
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=86ed1h6ppk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74467@debbugs.gnu.org \
--cc=binarin@binarin.info \
--cc=bjorn.bidar@thaodan.de \
--cc=yantar92@posteo.net \
/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.