zsh-workers
 help / color / mirror / code / Atom feed
From: Alexandre Duret-Lutz <duret_g@lrde.epita.fr>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
Cc: <zsh-workers@sunsite.auc.dk>
Subject: Re: :r modifier
Date: 14 Dec 2000 15:14:42 +0100	[thread overview]
Message-ID: <mvbae9z6qel.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of "Thu, 14 Dec 2000 16:00:05 +0300"

>>> "Andrej" == Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru> writes:

 >> 
 Bart> :Do we need to teach :h/:t about the leading-double-slash
 Bart> convention for some networked file systems?
 >> 
 >> I don't know, I never seen such file systems.

 Andrej> May be, you have heard about one. It is called Windows
 Andrej> and (sometimes) runs on x86 PC-compatible systems :-)

:o)

By the meantime I have been pointed to the Texinfo documentation
of Autoconf (>=2.49a) which reads as follow.

`dirname'
     Not all hosts have `dirname', but it is reasonably easy to
     emulate, e.g.:
          
          dir=`expr "x$file" : 'x\(.*\)/[^/]*' \|
                    '.'      : '.'

     But there are a few subtilities, e.g., under UN*X, should `//1'
     give `/'?  Paul Eggert answers:
          
          No, under some older flavors of Unix, leading `//' is a
          special path name: it refers to a "super-root" and is used to
          access other machines' files.  Leading `///', `////', etc.
          are equivalent to `/'; but leading `//' is special.  I think
          this tradition started with Apollo Domain/OS, an OS that is
          still in use on some older hosts.
          
          POSIX.2 allows but does not require the special treatment for
          `//'.  It says that the behavior of dirname on path names of
          the form `//([^/]+/*)?'  is implementation defined.  In these
          cases, GNU `dirname' returns `/', but it's more portable to
          return `//' as this works even on those older flavors of Unix.
          
          I have heard rumors that this special treatment of `//' may be
          dropped in future versions of POSIX, but for now it's still
          the standard.

 Andrej> I checked bash and it behaves the same as zsh. 

Huh?  You aren't speaking about :h here, are you?

 Andrej> On Cygwin bash is just as ignorant about special Win32
 Andrej> names as zsh is. It does not mean we should follow the
 Andrej> suite - but, at least, we are in good company as it
 Andrej> stand now :))
-- 
Alexandre Duret-Lutz


  reply	other threads:[~2000-12-14 14:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12 16:57 Alexandre Duret-Lutz
2000-12-13  4:15 ` Bart Schaefer
2000-12-13 13:03   ` Alexandre Duret-Lutz
2000-12-13 17:21     ` Bart Schaefer
2000-12-13 19:21       ` Alexandre Duret-Lutz
2000-12-13 23:10         ` Thomas Köhler
2000-12-14 13:00         ` Andrej Borsenkow
2000-12-14 14:14           ` Alexandre Duret-Lutz [this message]
2000-12-14 14:43             ` Andrej Borsenkow
2000-12-14 18:18               ` PATCH: " Alexandre Duret-Lutz
2000-12-14 23:52                 ` Geoff Wing
2000-12-15 10:22                   ` Alexandre Duret-Lutz
2000-12-15 10:58                     ` Geoff Wing
2000-12-15 10:27                 ` Peter Stephenson
2000-12-15 21:30                   ` Thomas Köhler
2000-12-15 11:53                 ` Alexandre Duret-Lutz
2001-02-14 18:34                   ` Alexandre Duret-Lutz
2001-02-14 18:40                     ` Peter Stephenson
2001-02-14 19:44                       ` Bart Schaefer
2001-02-19 10:32                   ` Peter Stephenson

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=mvbae9z6qel.fsf@phobos.lrde.epita.fr \
    --to=duret_g@lrde.epita.fr \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

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).