From: Barry Margolin <barmar@genuity.net>
Subject: Re: Another word for "path"?
Date: Wed, 22 Jan 2003 18:49:46 GMT [thread overview]
Message-ID: <eJBX9.35$rQ6.702@paloalto-snr1.gtei.net> (raw)
In-Reply-To: un0lthvyy.fsf@synopsys.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
In article <un0lthvyy.fsf@synopsys.com>,
David Masterson <dmaster@synopsys.com> wrote:
>>>>>> Barry Margolin writes:
>
>> In article <84u1g2cu7k.fsf@lucy.is.informatik.uni-duisburg.de>,
>> Kai Großjohann <kai.grossjohann@uni-duisburg.de> wrote:
>>> Pascal Bourguignon <pjb@informatimago.com> writes:
>
>>>> Whatever... Where have you seen 'path' defined this way?
>
>>> GNU coding standards. Since Tramp is a GNU program (or part of it,
>>> anyway), it's a good idea to adhere to this document :-)
>
>> Unix has always referred to something like /foo/bar/baz as a
>> pathname.
>
>I thought it always referred to as "filename". I think the term
>"pathname" became more prevalent after $PATH came into being (so it
>does go back a *long* way).
"filename" is often used to refer to the individual components of a
pathname, e.g. "foo", "bar", and "baz" are filenames.
The term "pathname" goes way back to the 60's -- it was used by Multics
designers.
>> I've always understood a list of directories like in $PATH to be
>> called a "search path", to distinguish it from a "file path".
>
>Didn't VMS have a "file path" type concept that was more akin to $PATH
>such that you could say "$PATH:file" and it would search the PATH for
>a "file"? Maybe it was also a concept in TOPS-20/10, but that's too
>far back for me to remember clearly.
I think they called them "logical devices", or something like that, because
you used them in a pathname in place of a disk device.
--
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
next prev parent reply other threads:[~2003-01-22 18:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 14:20 Another word for "path"? Kai Großjohann
2003-01-18 14:57 ` Romain FRANCOISE
2003-01-18 16:37 ` Kai Großjohann
2003-01-18 17:47 ` Billy O'Connor
2003-01-18 19:02 ` Romain FRANCOISE
2003-01-18 21:01 ` Andrew Markebo
2003-01-18 15:03 ` Alfred M. Szmidt
2003-01-18 19:43 ` Galen Boyer
2003-01-18 21:07 ` Harry Putnam
2003-01-18 21:28 ` David Kastrup
2003-01-18 21:42 ` Kai Großjohann
2003-01-18 21:35 ` Romain FRANCOISE
2003-01-18 22:28 ` gebser
2003-01-19 5:43 ` David Masterson
2003-01-19 20:21 ` Pascal Bourguignon
2003-01-21 17:02 ` Kai Großjohann
2003-01-21 18:23 ` Barry Margolin
2003-01-22 18:37 ` David Masterson
2003-01-22 18:49 ` Barry Margolin [this message]
2003-01-21 22:12 ` Johan Bockgård
2003-02-12 18:42 ` Daniel Barclay
2003-02-12 18:44 ` Daniel Barclay
[not found] ` <mailman.1885.1045075529.21513.help-gnu-emacs@gnu.org>
2003-02-13 7:28 ` Friedrich Dominicus
2003-02-13 9:32 ` Kai Großjohann
2003-02-13 15:42 ` Friedrich Dominicus
2003-02-13 17:09 ` Kai Großjohann
2003-02-13 21:40 ` Daniel Pfeiffer
2003-02-14 16:04 ` Rodney Sparapani
2003-02-14 17:09 ` Kai Großjohann
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 22:34 Bingham, Jay
[not found] <mailman.739.1043188595.21513.help-gnu-emacs@gnu.org>
2003-01-22 8:23 ` Kai Großjohann
2003-01-22 18:55 Bingham, Jay
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='eJBX9.35$rQ6.702@paloalto-snr1.gtei.net' \
--to=barmar@genuity.net \
/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).