From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pascal Quesseveur <pquessev@gmail.com>
Cc: 58464@debbugs.gnu.org
Subject: bug#58464: 28.1; browse-url-emacs doesn't work for local files on Windows
Date: Wed, 12 Oct 2022 13:09:41 +0200 [thread overview]
Message-ID: <87y1tlcn7u.fsf@gnus.org> (raw)
In-Reply-To: <82k055fsos.fsf@gmail.com> (Pascal Quesseveur's message of "Wed, 12 Oct 2022 08:43:15 +0200")
Pascal Quesseveur <pquessev@gmail.com> writes:
> emacs -Q
> (browse-url-emacs "file://C:/Windows/win.ini") -> Emacs hangs, nothing
> is displayed, C-g
That's the wrong syntax, but Emacs shouldn't hang...
> (browse-url-emacs "file:///C:/Windows/win.ini") -> file content is
> displayed, Message buffer contains:
>
> File exists, but cannot be read
> #<buffer win.ini</Windows>>
So it works fine when you use the right syntax for the URL, but the
problem is the misleading message? (Also noted in bug#42431 and
bug#58302 -- it's not Windows-specific, but a bug in all handling of
`file-name-handler-alist' for non-file "files".)
next prev parent reply other threads:[~2022-10-12 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 6:43 bug#58464: 28.1; browse-url-emacs doesn't work for local files on Windows Pascal Quesseveur
2022-10-12 7:26 ` Eli Zaretskii
2022-10-12 11:10 ` Lars Ingebrigtsen
2022-10-12 13:14 ` Eli Zaretskii
[not found] ` <828rlll4ef.fsf@gmail.com>
2022-10-12 13:04 ` Eli Zaretskii
2022-10-12 11:09 ` Lars Ingebrigtsen [this message]
2022-10-12 13:13 ` Eli Zaretskii
2022-10-12 13:18 ` Lars Ingebrigtsen
2022-10-12 14:25 ` Eli Zaretskii
2022-10-12 14:42 ` Lars Ingebrigtsen
2022-10-12 15:55 ` Eli Zaretskii
2022-10-12 15:57 ` Lars Ingebrigtsen
2022-10-12 16:07 ` Eli Zaretskii
2022-10-13 7:54 ` Lars Ingebrigtsen
2022-10-13 10:29 ` Eli Zaretskii
2022-10-13 11:30 ` Lars Ingebrigtsen
2022-10-13 15:44 ` Eli Zaretskii
2022-10-13 16:40 ` Paul Eggert
2022-10-13 19:15 ` Eli Zaretskii
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=87y1tlcn7u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58464@debbugs.gnu.org \
--cc=pquessev@gmail.com \
/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).