Cyrille Lefevre wrote at about 20:19:20 +0100 on Monday, February 7, 2011:
>
> Le 07/02/2011 19:03, Jeffrey J. Kosowsky a écrit :
> >
> > Is there any way to find (all) junction point using cygwin?
> > (if not possible in cygwin, can you point me to native win
> > functionality)
>
> how about the old dir one :-)
>
> ~ $ cmd /c dir /a:l
> ...
> R▒pertoire de C:\Users\Cyrille\Documents
>
> 17/12/2009 15:03 <JONCTION> Cygwin [\??\C:\cygwin\home\Cyrille]
> 24/09/2007 21:37 <JONCTION> Ma musique [C:\Users\Cyrille\Music]
> 28/09/2007 23:45 <JONCTION> Mes contacts [C:\Documents and
> Settings\Cyrille\Contacts]
> 24/09/2007 21:37 <JONCTION> Mes images [C:\Users\Cyrille\Pictures]
> 28/09/2007 23:44 <JONCTION> Mes liens [C:\Documents and
> Settings\Cyrille\Favorites]
> 28/09/2007 23:43 <JONCTION> Mes t▒l▒chargements [C:\Documents
> and Settings\Cyrille\Downloads]
> 24/09/2007 21:37 <JONCTION> Mes vid▒os [C:\Users\Cyrille\Videos]
>
> add /s for a recursive search
>
> well, that(s funny :
>
> /windows $ cmd /c dir /a:l /s
> ...
> Le nom de r▒pertoire C:\windows\System32\config\systemprofile\Local
> Settings\Application Data\Application Data\Application Data\Application
> Data\Application Data\Application Data\Application Data\Application
> Data\Microsoft\Windows\GameExplorer\{0AE259F7-4756-4B2B-883C-B5B1D0A4D346}
> est trop long.
> ...
>
> even windows commands fails one recursive junctions !
>
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.
where each source and target are full pathnames.
--
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
