all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pascal Bourguignon <pjb@informatimago.com>
Subject: Re: Another word for "path"?
Date: 19 Jan 2003 21:21:43 +0100	[thread overview]
Message-ID: <87y95ggaaw.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: 84hec65ylb.fsf@lucy.is.informatik.uni-duisburg.de

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> A Tramp filename consists of the following parts:
> 
>   - a method specification
>   - a user name
>   - a host name
>   - and a path specifying the file on the remote host
> 
> Now the GNU coding standards say that the word "path" is defined as a
> list of directories, such as those found in $PATH and $MANPATH.

Whatever... Where have you seen 'path' defined this way?

A path is  a path, and a path  to a file is a list  of directory entry
names, the last of  which is _a_ name of the file  and the other names
of directories.

$PATH and $MANPATH are misnomers  because they don't contain one path,
but a list of paths to the directories where commands or man pages are
to  be  searched.   At most  the  could  have  been named  $PATHS  and
$MANPATHS but better names would have been: $CMDDIRS and $MANDIRS.

Let's stop now with the novlang, and name your path 'path'!


> Which word could I use for the fourth component of a Tramp filename?
> I think "filename" is not a good word, as I already use it for the
> whole thing.

Obviously, the whole thing is a URL!  http://user@host/path
Why do you call it a Tramp file name?


-- 
__Pascal_Bourguignon__                   http://www.informatimago.com/
----------------------------------------------------------------------
There is a fault in reality. Do not adjust your minds. -- Salman Rushdie

  parent reply	other threads:[~2003-01-19 20:21 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y95ggaaw.fsf@thalassa.informatimago.com \
    --to=pjb@informatimago.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.