From: Lars Ingebrigtsen <larsi@gnus.org>
To: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
Cc: Michael Albinus <michael.albinus@gmx.de>, 40425@debbugs.gnu.org
Subject: bug#40425: 26.3; eww-open-file is not working with a Tramp file name
Date: Fri, 24 Jul 2020 17:02:26 +0200 [thread overview]
Message-ID: <87365hc5x9.fsf@gnus.org> (raw)
In-Reply-To: <86zh7qnh8t.fsf@duenenhof-wilhelm.de> (H. Dieter Wilhelm's message of "Thu, 23 Jul 2020 21:50:10 +0200")
dieter@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
next prev parent reply other threads:[~2020-07-24 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 11:25 bug#40425: 26.3; eww-open-file is not working with a Tramp file name H. Dieter Wilhelm
2020-07-17 14:39 ` Lars Ingebrigtsen
2020-07-17 17:35 ` Michael Albinus
2020-07-18 15:16 ` Lars Ingebrigtsen
2020-07-18 15:18 ` Michael Albinus
2020-07-18 15:36 ` Lars Ingebrigtsen
2020-07-18 16:04 ` Lars Ingebrigtsen
2020-07-23 19:50 ` H. Dieter Wilhelm
2020-07-24 15:02 ` Lars Ingebrigtsen [this message]
2020-07-24 16:25 ` Michael Albinus
2020-07-27 21:24 ` Lars Ingebrigtsen
2022-02-20 15:09 ` Lars Ingebrigtsen
2022-02-20 21:15 ` H. Dieter Wilhelm
2022-02-20 21:37 ` Lars Ingebrigtsen
2022-02-20 22:19 ` H. Dieter Wilhelm
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=87365hc5x9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40425@debbugs.gnu.org \
--cc=dieter@duenenhof-wilhelm.de \
--cc=michael.albinus@gmx.de \
/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).