GNU bug report logs - #40425
26.3; eww-open-file is not working with a Tramp file name

Previous Next

Package: emacs;

Reported by: dieter <at> duenenhof-wilhelm.de (H. Dieter Wilhelm)

Date: Sat, 4 Apr 2020 11:26:01 UTC

Severity: wishlist

Found in version 26.3

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: dieter <at> duenenhof-wilhelm.de (H. Dieter Wilhelm)
Cc: 40425 <at> debbugs.gnu.org, Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#40425: 26.3; eww-open-file is not working with a Tramp file
 name
Date: Fri, 24 Jul 2020 17:02:26 +0200
dieter <at> duenenhof-wilhelm.de (H. Dieter Wilhelm) writes:

> I'm providing a library for a programming mode (apdl-mode) where you can
> request manual entries for the language keywords.  Usually these html
> manuals are either stored in the cloud or locally on a workstation where
> you are, both, coding and running the finite element code.
>
> But now a user is applying Tramp to code remotely on his workstation and
> also wants to access the said html manual pages which are stored on his
> remote machine.
>
> Actually I think this is a reasonable use case for EWW. :-)

Yeah, that's true.  I've now reopened this bug report.

If the base document is fetched via Tramp, then relative links to
further documents via Tramp isn't a security concern at all.

I'm just wondering on what level this should be fixed at.  eww could add
further support for these relative links itself, or the url-file.el
library could grow some overrides to allow following Tramp file
names...  Hm...  The latter seems easier to implement, but I feel that
perhaps the former is what makes most sense.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 3 years and 145 days ago.

Previous Next


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