all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Brown <brown@fastmail.com>
Cc: 30195@debbugs.gnu.org
Subject: bug#30195: 26.0.91; emacs-26: eww incorrectly follows relative link in debian reference manual
Date: Fri, 13 Apr 2018 00:25:32 +0200	[thread overview]
Message-ID: <87h8ogdpur.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87k1wbds3v.fsf@fastmail.com> (Eric Brown's message of "Sun, 21 Jan 2018 11:44:20 -0600")

Eric Brown <brown@fastmail.com> writes:

> Tested with 'emacs -Q'.  The operating system is Debian Testing
> (buster), with emacs-26 head.
>
> With eww, browse to file:///usr/share/debian-reference.  This is the
> landing page which leads to the Debian Reference manuals various
> languages.
>
> Attempt to follow the link to English: HTML (multi files) and rather
> than going to:
>
> file:///usr/share/debian-reference/index.en.html
>
> eww attempts to go to:
>
> file:///usr/share/index.en.html
>
> instead of:
>
> file:///usr/share/debian-reference/index.en.html

The problem here is that file:///usr/share/debian-reference doesn't
exist.  But if you run url-retrieve on that, the URL library helpfully
roots around in that directory to see whether it can find a likely file
to display instead, and it finds
file:///usr/share/debian-reference/index.html.  But it doesn't report
this back to eww in any way, so eww thinks that the document is
file:///usr/share/debian-reference, and so all the references are wrong.

I don't really know what to do about this corner case...

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





  reply	other threads:[~2018-04-12 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 17:44 bug#30195: 26.0.91; emacs-26: eww incorrectly follows relative link in debian reference manual Eric Brown
2018-04-12 22:25 ` Lars Ingebrigtsen [this message]
2018-04-12 23:14   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8ogdpur.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=30195@debbugs.gnu.org \
    --cc=brown@fastmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.