unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuan Liu <yliu@stemnet.nf.ca.remove_this>
Subject: Re: NON-trivial regular expression problem (could not find on google)
Date: Fri, 24 Jan 2003 18:56:34 GMT	[thread overview]
Message-ID: <3E318DFC.30709@stemnet.nf.ca.remove_this> (raw)
In-Reply-To: fe4612a5.0301200115.241f7088@posting.google.com

Peter J. Acklam wrote:
> "Dr. Yuan Liu" <yliu@stemnet.nf.ca.remove_this> wrote:
> 
> 
>>Bournish and Kornish shells all stick with the symbolic
>>path, i.e., foo/bar/.. is always foo.
> 
> 
> Take a look at the following -- it is an example of a case where
> "foo/bar/.." and "foo" is not the same (ksh on Solaris 8):
> 
>     /var/tmp $ mkdir -p foo/fee/fie/foe
>     /var/tmp $ ln -s fee/fie/foe foo/bar
>     /var/tmp $ ls foo
>     bar  fee
>     /var/tmp $ ls foo/bar/..
>     foe

Interesting.  ls and pwd, cd behave differently.  Thanks for pointing out.

Yuan Liu

> In this case, "foo/bar/.." is "foo/fee/fie/foe/.." which is
> "foo/fee/fie" which is *not* the same as "foo".  The reason
> is simply that "foo/bar/.." resolves to a different directory
> than "foo".  So, you can *not* assume "foo/bar/.." is "foo".
> 
> Peter

  reply	other threads:[~2003-01-24 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-18 20:19 NON-trivial regular expression problem (could not find on google) Instant Democracy
2003-01-18 21:38 ` Harry Putnam
2003-01-18 21:46 ` Kai Großjohann
2003-01-18 22:52 ` AW
2003-01-18 23:03 ` Edi Weitz
2003-01-19  0:27 ` Larry Clapp
2003-01-19  0:36 ` Dr. Yuan Liu
2003-01-19  0:53 ` John W. Krahn
2003-01-19  1:05 ` William Park
2003-01-19 12:17 ` Peter J. Acklam
2003-01-19 19:26   ` Dr. Yuan Liu
2003-01-20  9:15     ` Peter J. Acklam
2003-01-24 18:56       ` Yuan Liu [this message]
2003-01-24 11:20 ` Bruce Barnett

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=3E318DFC.30709@stemnet.nf.ca.remove_this \
    --to=yliu@stemnet.nf.ca.remove_this \
    /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).