zsh-users
 help / color / mirror / code / Atom feed
From: Mircea Damian <dmircea@secu.kappa.ro>
To: "Larry P . Schrof" <schrof@cig.mot.com>
Cc: zsh-users@sunsite.auc.dk
Subject: Re: is this normal?
Date: Mon, 1 Mar 1999 19:44:55 +0200	[thread overview]
Message-ID: <19990301194455.A12222@kappa.ro> (raw)
In-Reply-To: <199903011610.LAA29744@po_box.cig.mot.com>; from Larry P . Schrof on Mon, Mar 01, 1999 at 10:08:24AM -0600

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

On Mon, Mar 01, 1999 at 10:08:24AM -0600, Larry P . Schrof wrote:
> First, remember that in the / directory, the file .. just points back
> to / itself.
This is normal. That is why this happens:

root@taz:~# cd /
root@taz:/# cd ../bin/..
root@taz:/..#                      <-- here /.. == /

But then it looks very odd to me  when I try multiple "../" constructions
like:


root@taz:~# cd /
root@taz:/# cd ../../bin
root@taz:/bin#                                  <-- why not /../../bin
root@taz:/bin# cd /
root@taz:/# cd ../../../bin
root@taz:/../bin# cd /
root@taz:/# cd ../../../../bin
root@taz:/bin#

As far as I see this happens only when the number of "../" is odd so I
think that this is a bug!



> lyric[93] RPROMPT='$(pwd)'                                              /../etc
> lyric[94]                                                                  /etc
As you said, this is only a quick but dirty fix. :-(


-- 
Mircea Damian
Network Manager
dmircea@roedu.net, dmircea@lbi.ro, dmircea@kappa.ro
MD65-RIPE, MD2225, MD1-6BONE

[-- Attachment #2: Type: application/pgp-signature, Size: 248 bytes --]

  reply	other threads:[~1999-03-01 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-28 19:11 Mircea Damian
1999-03-01 16:08 ` Larry P . Schrof
1999-03-01 17:44   ` Mircea Damian [this message]
1999-03-01 18:51     ` Sweth Chandramouli

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=19990301194455.A12222@kappa.ro \
    --to=dmircea@secu.kappa.ro \
    --cc=schrof@cig.mot.com \
    --cc=zsh-users@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).