GNU bug report logs - #57572
29.0.50; Tramp error with tramp-file-name-unify

Previous Next

Package: emacs;

Reported by: Thierry Volpiatto <thievol <at> posteo.net>

Date: Sun, 4 Sep 2022 07:17:01 UTC

Severity: normal

Merged with 57676

Found in version 29.0.50

Fixed in version 29.1

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #49 received at 57572 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Thierry Volpiatto <thievol <at> posteo.net>
Cc: 57572 <at> debbugs.gnu.org
Subject: Re: bug#57572: 29.0.50; Tramp error with tramp-file-name-unify
Date: Sun, 11 Sep 2022 15:08:39 +0200
Thierry Volpiatto <thievol <at> posteo.net> writes:

> Hello Michael,

Hi Thierry,

>> non-essential is a mean to tell Tramp, that it shouldn't open a
>> connection when it isn't established yet.
>
> Yes, it is what I always understood but I am now confused because the
> connection is trigerred by file-accessible-directory-p even with
> non-essential==t.

Well, non-essential is not checked for *all* basic functions. Its most
important use is to prevent expand-file-name and file-exists-p from
action. See function tramp-connectable-p, and its use in tramp.el and
tramp-sh.el.

Why it has triggered file-accessible-directory-p to go remote I cannot
analyze w/o traces.

>> That's why you bind it in helm to t. Of course it will work when you
>> don't bind it.
>
> It is bound to t on top but it is nil in helm-find-files-get-candidates.

Well, this lets Tramp connect.

>> But then, there are other problems.
>
> Yes of course but only if I bind it on top, isn't it?

Wherever you bind it. If a Tramp function is called, and non-essential
is nil, Tramp is likely to go remote. If you want it, fine.

Best regards, Michael.




This bug report was last modified 2 years and 255 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.