Corinna Vinschen wrote: > On Jan 17 14:56, Corinna Vinschen wrote: > > ...we won't take patches which add arbitrary options to the CYGWIN > > variable which could also be solved in other ways. In this special > > case, only the conversion from POSIX to Win32 paths is affected. > > This conversion is only supported by the cygwin_conv_path function > > and, subsequently, the cygpath utility. Therefore, such a change > > should be restricted to this API. I'll have a look into adding > > something along these lines. > > Try the latest developer snapshot from http://cygwin.com/snapshots/ > It contains a patch which should help in most cases.
It works in many places, but not always. In particular, the path ".." when the current ($PWD) directory is a junction is interpreted along the lines as a symlink: to the parent of the target. I do enough file operations between parent and child, where the child is a junction, that I'll stick with my own patch. Another inconsistency in it is shown in this dialog: ~/incoming/dl$ pwd /home/barrkel/incoming/dl ~/incoming/dl$ cygpath -aw . M:\mathom\_c_Documents and Settings_barrkel_Downloads ~/incoming/dl$ cygpath -aw $PWD C:\cygwin\home\barrkel\incoming\dl ~/incoming/dl$ cygpath -aw $PWD/. M:\mathom\_c_Documents and Settings_barrkel_Downloads ~/incoming/dl$ cygpath -aw $PWD/.. C:\cygwin\home\barrkel\incoming $PWD/. is at odds with $PWD and $PWD/.. -- Barry -- http://blog.barrkel.com/ -- 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
