From: "Alexandre Billon" <abillon@gmail.com>
Subject: Re: links down
Date: Mon, 20 Feb 2006 17:41:10 +0100 [thread overview]
Message-ID: <b78ca0f80602200841k1b9c1461n@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00602200832k58629aa6g6bcf7ab777dc40e7@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]
I seems to me that you can get to the right place by replacing the .pdf by a
.html and by clicking on the link that appears on the html page. Not a
definitive solution though...
2006/2/20, Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
>
> On 2/20/06, andrea valle wrote:
> > Hi to all,
> >
> > I'm having many of these while searching for sample in contextgarden:
> >
> > request http://www.pragma-ade.com/general/manuals/mag-0001.pdf cannot
> > be honored
>
> Oh, it's http://www.pragma-ade.com/general/magazines/mag-0001.pdf
> (magazines, not manuals). I guess it was probably me who replaced many
> hard coded links by [[manual:mag-0001.pdf]] (as in this example)
> without ever testing them. I wasn't aware of this problem (I never
> thought about documents outside the "manuals" folder).
>
> Patrick, are you going to fix the source so that these links will
> point to the proper document s or should I fix those links (hard code
> them) again?
>
> Is there any simple tool to check for broken link in the wiki?
>
> Mojca
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
[-- Attachment #1.2: Type: text/html, Size: 1744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-02-20 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 14:14 andrea valle
2006-02-20 16:32 ` Mojca Miklavec
2006-02-20 16:41 ` Alexandre Billon [this message]
2006-02-21 14:30 ` Patrick Gundlach
2006-02-21 19:12 ` Mojca Miklavec
2006-02-20 21:54 ` Hans Hagen
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=b78ca0f80602200841k1b9c1461n@mail.gmail.com \
--to=abillon@gmail.com \
--cc=ntg-context@ntg.nl \
/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).