Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Thompson <gregt@visix.com>
Subject: Re: still one smiley glitch
Date: 18 Jul 1996 15:37:40 -0400	[thread overview]
Message-ID: <1lybkh73p7.fsf@zagato.visix.com> (raw)
In-Reply-To: Richard Pieri's message of 18 Jul 1996 13:20:36 -0400

>"RP" == Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:

  RP> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

  PA> I meant the root of the current http server, i.e. local compared to
  PA> the current document) .  Like this

  RP> You mean a relative document reference.  Those are properly set
  RP> up like this:

  RP> for an absolute local reference:
  RP> <a href="/home/ratinox/Bookmarks.html">...</a>
  RP> and for a relative local reference:
  RP> <a href="Bookmarks.html">...</a>

  RP> with no lookup type.

  RP> Neither of these are valid URLs, though they are valid HTML.
  RP> URLs are unambiguous, human-readable addresses.  A valid URL has
  RP> this format:

  RP> 	The URL specifier "<URL" at the beginning of the line
  RP> 	The type of lookup
  RP> 	The colon-slash-slash delimiter
  RP> 	A host name (should be fully qualified)
  RP> 		Optionally a colon and port number
  RP> 	A slash delimiter
  RP> 		Optionally a directory path or path to file.  If a
  RP> 		directory then there must be a trailing slash.
  RP> 	The URL closure ">" and nothing else on the line.

this is not true.  <URL:> has nothing to do with proper url syntax.
it has become common convention when embedding a url in a piece of
mail or something, but a url does not need that stuff around it.  it
sounds like you are describing a convention for putting a url in a
message, not the proper syntax of a url.
-- 
		-greg	   a fire in its heart will not let it die. it
			      roars + fumes + cries all day.  shoot me
			   out the sky. pop!  pop! down goes the enemy
								-rodan


  reply	other threads:[~1996-07-18 19:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-17 17:25 Karl Kleinpaste
1996-07-17 18:40 ` Richard Pieri
1996-07-17 19:37   ` Karl Kleinpaste
1996-07-17 18:49 ` William Perry
1996-07-17 19:10   ` Per Abrahamsen
1996-07-17 19:43     ` Kai Grossjohann
1996-07-18 13:40     ` Richard Pieri
1996-07-18 13:44       ` Lars Balker Rasmussen
1996-07-18 14:06       ` Greg Thompson
1996-07-18 14:08       ` Per Abrahamsen
1996-07-18 17:20         ` Richard Pieri
1996-07-18 19:37           ` Greg Thompson [this message]
1996-07-19 14:17             ` Richard Pieri
1996-07-19 20:24               ` Steven L Baur

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=1lybkh73p7.fsf@zagato.visix.com \
    --to=gregt@visix.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.
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).