unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Emery <see.sig@spamfoil.invalid>
Subject: Re: Emacs 21 and w3 on Debian
Date: Sun, 22 May 2005 22:14:11 +0200	[thread overview]
Message-ID: <874qcvqar0.fsf@spamfoil.invalid> (raw)
In-Reply-To: 87sm0fbjx4.fsf@tiger.rapttech.com.au

Tim X <timx@spamto.devnul.com> writes:

> It seems that
> there is a problem with relative links within w3 and I wanted to know
> if anyone else has seen this and possibly has a solution. 

I have never experienced such a problem ; do you have an example
that is accessible on internet ?

> For example, if I'm at the page
>
> http://www.some.host/dir/index.html
>
> and that page has a url of the form <a href="about/index.html">next
> link</a>, tabbing to that link and hitting enter causes w3 to try and
> retrieve the url http://www.some.host/about/index.html when it should
> be trying to retrieve http://www.some.host/dir/about/index.html.

A wild guess: is there an erroneous
<base href="http://www.some.host/index.html">
in http://www.some.host/dir/index.html ?

Thierry
-- 
thierry |dot| emery |at| free |dot| fr

  reply	other threads:[~2005-05-22 20:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22 11:05 Emacs 21 and w3 on Debian Tim X
2005-05-22 20:14 ` Thierry Emery [this message]
2005-05-22 22:27   ` Tim X
2005-05-23  7:49     ` Tim X
     [not found]     ` <d6rt02$cho$1@news.sap-ag.de>
2005-05-23  7:53       ` Tim X
2005-05-23  9:09         ` Thierry Emery
     [not found]           ` <d6sa8f$mmu$1@news.sap-ag.de>
2005-05-23 17:22             ` Thierry Emery
2005-05-24  5:48               ` Klaus Straubinger
2005-05-24 16:39                 ` Thierry Emery
2005-05-24  8:19           ` Tim X
     [not found]           ` <d71mbu$ka$1@news.sap-ag.de>
2005-05-25 17:28             ` Thierry Emery
2005-05-26 10:11               ` Thierry Emery
2005-05-27  6:15                 ` Klaus Straubinger
2005-05-27 19:09                   ` Thierry Emery
2005-05-30  6:33                     ` Klaus Straubinger
2005-05-25 17:52             ` Kevin Rodgers
     [not found]             ` <mailman.1793.1117044330.25862.help-gnu-emacs@gnu.org>
2005-05-27  6:29               ` Klaus Straubinger
2005-05-27 16:35                 ` Kevin Rodgers
     [not found]                 ` <mailman.2099.1117212347.25862.help-gnu-emacs@gnu.org>
2005-05-30  6:26                   ` Klaus Straubinger
2005-05-31 16:41                     ` Kevin Rodgers
     [not found]                     ` <mailman.2623.1117558050.25862.help-gnu-emacs@gnu.org>
2005-06-01  6:19                       ` Klaus Straubinger
2005-06-01 15:57                         ` Stefan Monnier
2005-06-02  6:42                           ` Klaus Straubinger
2005-06-05 23:08                             ` Stefan Monnier
2005-06-01 15:55                       ` Stefan Monnier
     [not found]         ` <d6s5b2$itm$1@news.sap-ag.de>
2005-05-24  8:17           ` Tim X
2005-05-23  8:30     ` Thierry Emery
     [not found]       ` <d6s68c$jsf$1@news.sap-ag.de>
2005-05-23  9:57         ` Thierry Emery
     [not found]           ` <d6sble$nnv$1@news.sap-ag.de>
2005-05-23 17:25             ` Thierry Emery
2005-05-24  8:24       ` Tim X

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=874qcvqar0.fsf@spamfoil.invalid \
    --to=see.sig@spamfoil.invalid \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).