From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Absolute pathnames on cygwin
Date: Fri, 20 Oct 2000 08:06:12 +0000 [thread overview]
Message-ID: <1001020080613.ZM8095@candle.brasslantern.com> (raw)
In-Reply-To: <001d01c039db$fb803b80$21c9ca95@mow.siemens.ru>
On Oct 19, 6:50pm, Andrej Borsenkow wrote:
}
} I believe, it makes no sense to try to recognize all possible
} forms of Windows pathnames in Zsh - rather, we should simply call
} [cygwin_conv_to_posix_path] and deal with single Unix form. The only
} problem is, when should such function be called.
}
} There are possibly other places where this may cause confusion.
There are probably a very large number of such places; think of all the
places where Clint just finished removing references to PATH_MAX.
Think of all the shell functions that manipulate paths with $x:h, $x:t,
${x#*/}, ${x%/*}, [[ $x == /* ]], etc.
The problem is only going to "go away" when the user stops referring to
Windows drives by `x:' and uses the /cygdrive form exclusively. Otherwise
no matter how good a job zsh does of catching `x:' when it manipulates a
string it knows internally is a path name, there's a potential for strings
that it *doesn't* know are path names to become "mangled" (and then later
used as a path name, when it's too late for zsh to fix it).
This is not to say that we shouldn't try to fix e.g. `cd' to do the right
thing as often as possible, but that the general problem of nonuniform path
formats is very difficult except in a rigid UI where pathnames are never
entered except in pathname-typed input boxes.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-10-20 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 14:50 Andrej Borsenkow
2000-10-20 8:06 ` Bart Schaefer [this message]
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=1001020080613.ZM8095@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).