From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: zsh-users@sunsite.dk
Subject: Re: Convert absolute paths to relative paths
Date: Sun, 21 Apr 2002 18:32:00 +0000 [thread overview]
Message-ID: <1020421183201.ZM16791@candle.brasslantern.com> (raw)
In-Reply-To: <m2u1q7x9ez.fsf@zion.rcn.com>
On Apr 20, 12:48am, Vin Shelton wrote:
} Subject: Re: Convert absolute paths to relative paths
}
} It turned out I did care about minimizing the path, so here's what I
} came up with:
That's a more interesting algorithm than mine. Assorted suggestions ...
} [[ $1 != /* ]] && print $1 && return
Add something like:
[[ -f $1 ]] && 1=$1:h
[[ -d $1 ]] || return 1
} local dir=${2:-$PWD}
} [[ $1 == $dir ]] && print . && return
Replace with:
[[ $1 -ef ${2:=$PWD} ]] && print . && return
} cur=(${(ps:/:)dir}) # Split 'current' directory into cur
} abs=(${(ps:/:)1}) # Split target directory into abs
You don't need the (p) flag there, you aren't using any prompt escapes.
To be really thorough, you should also eliminate any uses of ./ or ../
in either path.
} # Figure out how many parents to get to common root
} local relpath=
} while ((i <= $#cur))
} do
} relpath=../$relpath
} ((i=i+1))
} done
Replace with:
local relpath=${(j:/:)cur/*/..}
} relpath=$relpath${(j:/:)abs}
} print ${relpath%/}
In case of symlinks, you should test that the resulting $relpath actually
exists.
So the whole thing becomes:
---- 8< ----
# Print the a relative path from the second directory to the first,
# defaulting the second directory to $PWD if none is specified.
emulate -L zsh || return 1
[[ $1 != /* ]] && print $1 && return
[[ -f $1 ]] && 3=$1:t 1=$1:h
[[ -d $1 && -d ${2:=$PWD} ]] || return 1
[[ $1 -ef $2 ]] && print ${3:-.} && return
# The simplest way to eliminate symlinks and ./ and ../ in the paths:
1=$(cd $1; pwd -r)
2=$(cd $2; pwd -r)
local -a cur abs
cur=(${(s:/:)2}) # Split 'current' directory into cur
abs=(${(s:/:)1} $3) # Split target directory into abs
# Compute the length of the common prefix, or discover a subdiretory:
integer i=1
while [[ i -le $#abs && $abs[i] == $cur[i] ]]
do
((++i > $#cur)) && print ${(j:/:)abs[i,-1]} && return
done
2=${(j:/:)cur[i,-1]/*/..} # Up to the common prefix directory and
1=${(j:/:)abs[i,-1]} # down to the target directory or file
print $2${1:+/$1}
--
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:[~2002-04-21 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 11:49 Vin Shelton
2002-04-19 17:51 ` Bart Schaefer
2002-04-19 19:00 ` Bart Schaefer
2002-04-20 0:47 ` Vin Shelton
2002-04-20 0:59 ` Bart Schaefer
2002-04-20 4:48 ` Vin Shelton
2002-04-21 18:32 ` 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=1020421183201.ZM16791@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=acs@alumni.princeton.edu \
--cc=zsh-users@sunsite.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).