unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pquessev@gmail.com, 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 15:18:10 +0200	[thread overview]
Message-ID: <87mta1b2p9.fsf@gnus.org> (raw)
In-Reply-To: <83czaxchgp.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Oct 2022 16:13:58 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> No, the misleading message is likely just a symptom of the root
> cause.  The root cause is that the buffer-file-name is set
> incorrectly, and likewise the default-directory.

Well...  have a look at bug#bug#42431, it analyses the problem.  (Which
is that any usage if insert-file-contents that doesn't reference an
actual file on the file system will signal an error, and that's a
mistake, I think?)






  reply	other threads:[~2022-10-12 13:18 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
2022-10-12 13:13   ` Eli Zaretskii
2022-10-12 13:18     ` Lars Ingebrigtsen [this message]
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=87mta1b2p9.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58464@debbugs.gnu.org \
    --cc=eliz@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).