From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>, 40425@debbugs.gnu.org
Subject: bug#40425: 26.3; eww-open-file is not working with a Tramp file name
Date: Sat, 18 Jul 2020 17:36:57 +0200 [thread overview]
Message-ID: <87lfjgltra.fsf@gnus.org> (raw)
In-Reply-To: <87zh7wu9zz.fsf@gmx.de> (Michael Albinus's message of "Sat, 18 Jul 2020 17:18:56 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
>> Thanks... eww would have to delete the local copy of the file after
>> rendering, I guess?
>
> Yes. And it should handle links to relative files similar.
I'm not sure I follow you. Why should eww copy files that are pointed
to by relative URLs?
Anyway, I'm not very enthusiastic at the idea of making local file
copies -- cleaning up isn't guaranteed (if Emacs crashes, for instance),
and files left behind may be a security concern.
Perhaps eww-open-file could just be rewritten to load the file into a
temporary buffer, parse it and then render it, and avoid the URL library
altogether... I don't see any huge downside to doing it that way.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-07-18 15:36 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 [this message]
2020-07-18 16:04 ` Lars Ingebrigtsen
2020-07-23 19:50 ` H. Dieter Wilhelm
2020-07-24 15:02 ` Lars Ingebrigtsen
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=87lfjgltra.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).