From: "Jeffrey J. Kosowsky" <cygwin@kosowsky.org>
To: Cyrille Lefevre <cyrille.lefevre-lists@laposte.net>
Cc: cygwin@cygwin.com
Subject: Re: Finding junction points
Date: Mon, 07 Feb 2011 19:59:00 -0000 [thread overview]
Message-ID: <19792.20228.470412.230374@consult.pretender> (raw)
In-Reply-To: <4D504C02.9090506@laposte.net>
Cyrille Lefevre wrote at about 20:46:10 +0100 on Monday, February 7, 2011:
>
> Le 07/02/2011 20:25, Jeffrey J. Kosowsky a écrit :
> > Yes - that is one of my two problems:
> > 1. It gets messed up on loops created by its own junctions
> > 2. The format of the output is a bit difficult to parse since you have
> > to go back up to see what directory you are in.
> >
> > Ideally, I would like to have the output in 2-columns like:
> > source1 target1
> > source 2 target2
> > etc.
>
> something like this ?
>
> cmd /c dir /a:l /n | awk '/^ /{$1=$2="";sub(/^
> +/,"");d=$0;next}/JONCTION/{sub(/.*<JONCTION> +/,"");sub(/\[/, "->
> ");sub(/\]$/, ""); print d "\\" $0}'
>
Yes that is helpful (though at least in English one needs to use
JUNCTION rather than JONCTION :) and I added >/dev/null to capture the
"too long" lines.
However, it still has the problem we both identified of capturing
many duplicates and loops (until one gets them too long).
For example,
C:\Documents and Settings\Default User ->C:\Users\Default
is a duplicate of:
C:\Users\Default User ->C:\Users\Default
To do this right, one would want to stop the recursion as soon as a
junction is found since recursing down the junction will by definition
create duplicates.
The recursion one wants is something like (in pseudo code)
find_junctions(dir) {
for 'each' entry in dir {
if entry is a junction, then print junction
if 'entry' is a directory, find_junction(entry)
}
}
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-07 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 18:04 Jeffrey J. Kosowsky
2011-02-07 19:19 ` Cyrille Lefevre
2011-02-07 19:26 ` Jeffrey J. Kosowsky
2011-02-07 19:46 ` Cyrille Lefevre
2011-02-07 19:59 ` Jeffrey J. Kosowsky [this message]
2011-02-07 20:05 ` Jeffrey J. Kosowsky
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=19792.20228.470412.230374@consult.pretender \
--to=cygwin@kosowsky.org \
--cc=cygwin@cygwin.com \
--cc=cyrille.lefevre-lists@laposte.net \
/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).