From: Katsumi Yamaoka <yamaoka@jpl.org>
To: jidanni@jidanni.org
Cc: ding@gnus.org, emacs-w3m@namazu.org
Subject: [emacs-w3m:10715] Re: nnrss: relative links in message bodies
Date: Fri, 20 Feb 2009 14:52:16 +0900 [thread overview]
Message-ID: <b4m7i3l8xkf.fsf@jpl.org> (raw)
In-Reply-To: <87ljs14suo.fsf@jidanni.org>
>>>>> jidanni@jidanni.org wrote:
> What should nnrss do when encountering a link like:
> <p>Bob, the fact is that the Israeli government ... refugee relief
> aid; see my <a href="../04/on-netanyahu-on-gaza">previous letter</a>.
The base tag, like <base href="http://host/directory/">, in the
<head>...</head> section is needed to expand relative links to
the absolute ones. If it exixts, emacs-w3m, an html renderer
for Gnus, should handle it properly. The base tag is often
omitted in html data. Even in such a case, shimbun (bundled
with emacs-w3m) uses the directory of the current page address
to generate the base tag. However, IIUC, nnrss doesn't.
> When tabbed to, we see "buffer://../04/on-netanyahu-on-gaza".
> What is this "buffer:" protocol? A red flag that there is a bug.
The `buffer:' scheme is for the emacs-w3m internal. It is mainly
for accessing `name' tags within an html article. Maybe emacs-w3m
misidentifies it as a name link because of no base tag.
;; BTW, this feature has been made by your request. ;-)
;; Cf. <b4mbpynrbmw.fsf@jpl.org>
> Why can't it detect that this is a relative link?
To make it work, nnrss.el needs to be improved further.
Regards,
next prev parent reply other threads:[~2009-02-20 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 4:47 jidanni
2009-02-20 5:52 ` Katsumi Yamaoka [this message]
2009-02-20 6:03 ` [emacs-w3m:10716] " jidanni
2009-02-20 23:43 ` [emacs-w3m:10715] " Kevin Ryde
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=b4m7i3l8xkf.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-w3m@namazu.org \
--cc=jidanni@jidanni.org \
/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.
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 NNTP newsgroup(s).