From: wmperry@gnu.org (William M. Perry)
Subject: Re: WIBNI there was a URL-syntax way of referring to the manual?
Date: Sat, 18 Aug 2001 13:03:30 -0500 [thread overview]
Message-ID: <867kw1qm8d.fsf@hel.bp.aventail.com> (raw)
In-Reply-To: <ilug0aplhnr.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 18 Aug 2001 13:41:12 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Janne Rinta-Manty <rintaman@cs.Helsinki.FI> writes:
>
>> >> That is, what if "info://Gnus/Select_Methods" pulled up the Gnus
>>>> *Info* pages and picked off section "Select Methods"? And
>>>> "info://Message/Mail_Variables" did the similar obvious thing?
>>
>> ZSH> Sounds cool. The hack is `+' -> SPC or "%20". Try
>> ZSH> info://Gnus/Select%20Methods
>> ZSH> info://Message/Mail+Variables
>>
>> Cool! But IMHO it would be better if it were info:/Foo/Bar, not with
>> the double slash, conforming to the Generic URI syntax in RFC 2396.
>
> KDE's konqueror support these kind of URLs for browsing info files.
>
> info:/dir
> info:/am-utils/Top
> info:/am-utils/Supported Platforms
*sigh* I wish people would look around before implementing stuff like
this. Emacs/W3 supported info: URLs for ages and uses the #target notation
to specify a node. Seems a bit more in keeping with what #foo is supposed
to mean in general URL syntax.
-bp
--
Ceterum censeo vi esse delendam
next prev parent reply other threads:[~2001-08-18 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 3:44 Karl Kleinpaste
2001-08-18 6:05 ` ShengHuo ZHU
2001-08-18 7:35 ` Christoph Conrad
2001-08-18 8:32 ` Janne Rinta-Manty
2001-08-18 11:41 ` Simon Josefsson
2001-08-18 18:03 ` William M. Perry [this message]
2001-08-18 10:06 ` Lars Magne Ingebrigtsen
2001-09-01 16:40 ` Dave Love
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=867kw1qm8d.fsf@hel.bp.aventail.com \
--to=wmperry@gnu.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).