From: Felix Dietrich <felix.dietrich@sperrhaken.name>
To: help-gnu-emacs@gnu.org
Subject: Re: Error with tramp-archive-autoload-file-name-handler
Date: Sat, 02 Apr 2022 14:00:51 +0200 [thread overview]
Message-ID: <877d873dak.fsf@sperrhaken.name> (raw)
In-Reply-To: <87pmm11sdw.fsf@web.de> (Michael Heerdegen's message of "Fri, 01 Apr 2022 03:53:15 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I've found out a bit more background I think:
>
> When I start Emacs, tramp-archive-enabled is t. But loading
> tramp-archive.el sets it to nil (probably because some dependencies are
> missing). I guess that for you it is still t, and that's the reason why
> the recipe(s) didn't work for you.
Did you compile Emacs without D-Bus support and/or is Emacs unable to
run gvfsd-fuse? This seems to be what decides the value of
‘tramp-gvfs-enabled’, which is, at a quick glance, used to set
‘tramp-archive-enabled’ (in tramp-archive.el and tramp-gvfs.el,
respectively).
> Anyway, when `tramp-archive-autoload-file-name-handler' is present after
> tramp-archive-enabled has become nil, it is used and called but doesn't
> handle the request (i.e. returns nil). AFAIU, that was what I have been
> seeing.
Could the tramp error handler provide a more helpful error message in
cases where it currently just returns nil? Or are there limitations
prohibiting this, for example in how Emacs processes file handlers?
--
Felix Dietrich
next prev parent reply other threads:[~2022-04-02 12:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 23:44 Error with tramp-archive-autoload-file-name-handler Michael Heerdegen
2022-03-26 8:39 ` Michael Albinus
2022-03-26 19:01 ` Michael Heerdegen
2022-03-27 0:06 ` Michael Heerdegen
2022-03-27 8:33 ` Michael Albinus
2022-03-28 2:20 ` Michael Heerdegen
2022-03-28 6:08 ` Felix Dietrich
2022-03-28 10:25 ` Michael Albinus
2022-03-29 0:17 ` Michael Heerdegen
2022-03-29 7:30 ` Michael Albinus
2022-04-01 1:53 ` Michael Heerdegen
2022-04-02 12:00 ` Felix Dietrich [this message]
2022-04-02 17:00 ` Michael Albinus
2022-04-06 8:49 ` Felix Dietrich
2022-04-06 18:13 ` Michael Albinus
2022-04-07 10:14 ` Michael Albinus
2022-04-07 17:54 ` Felix Dietrich
2022-04-08 9:41 ` Michael Albinus
2022-04-13 2:03 ` Michael Heerdegen
2022-04-03 1:26 ` Michael Heerdegen
2022-04-03 15:57 ` Michael Albinus
2022-04-04 0:58 ` Michael Heerdegen
2022-04-04 7:40 ` Michael Albinus
2022-03-29 0:09 ` Michael Heerdegen
2022-03-27 8:16 ` Michael Albinus
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=877d873dak.fsf@sperrhaken.name \
--to=felix.dietrich@sperrhaken.name \
--cc=help-gnu-emacs@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.
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).