lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Improper ~/ expansion in file://


From: David Combs
Subject: Re: lynx-dev Improper ~/ expansion in file://
Date: Sun, 22 Nov 1998 16:44:54 -0800 (PST)

> From address@hidden Sun Nov 22 14:35:06 1998
> Date: Sun, 22 Nov 1998 16:33:45 -0600 (CST)
> From: Klaus Weide <address@hidden>
> To: address@hidden
> Subject: Re: lynx-dev Improper ~/ expansion in file://
> In-Reply-To: <address@hidden>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Sender: address@hidden
> Precedence: bulk
> Reply-To: address@hidden
> 
> On Fri, 20 Nov 1998, Ryan Hung wrote:
> 
> > On Fri, 20 Nov 1998, Klaus Weide wrote:
> > >   The problem
> > > should be solved where it is generated, which is where the /~ is replaced
> > > by something else.
> > 
> > Hmm, I see.  But where would "//" in a real pathname be appropriate?
> 
> A good question.  I don't know the real answer, but "\\" in Windows (which
> probably would be translated into "//") has a specific meaning, and I seem
> to recall that POSIX or some similar spec for Unix says something like
> "a // at the beginning may have system-defined meaning". (Can anyone
> confirm?)
> 
<snip>

I don't know what relevance this might or mignt not have, but
what emacs does when it sees // when you enter a file-name is
to throw away anything to its left.  At least that's what it does
for me, when it has a default in its prompt, and I just 
enter (actually, append) "//home/dkc/...", ie it lets 
the slash just before "home" mean "root".

(obviously, you don't do that to http//:... but I bet emacs 
does, never tried it though)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]