This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CWD and long paths


On Tue, 16 Oct 2007, Igor Peshansky wrote:

> On Fri, 12 Oct 2007, Lev Bishop wrote:
>
> > On 10/12/07, Corinna Vinschen wrote:
> >
> > > In Cygwin we can do as we like, so we can handle CWDs with long path
> > > names without problems.  Unfortunately we have to call non-Cygwin
> > > applications once in a while and then it gets weird.
> > >
> > > So, here's the question: How should we handle the CWD in future?
> > >
> > > - We could stick to only supporting CWDs of MAX_PATH length so we don't
> > >   have a problem when calling native apps.
> > >
> > > - We could support long CWDs and change the CWD to the longest path
> > >   prefix <= MAX_PATH as soon as we call a native app.
> > >
> > > - Something else?
> >
> > Something like:
> >
> > subst t: prefix\of\long\path
> > t:
> > cd rest\of\long\path
> > win32_command
> > subst /d t:
> >
> > This allows to get up to 2*MAX_PATH and can be iterated to get deeper.
> >
> > Ugly, I know, but maybe better than the alternatives?
>
> Wouldn't it be better to use reparse points if we have NTFS?
> 	Igor

...And I should have read the whole thread.  Apologies for the noise.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Belief can be manipulated.  Only knowledge is dangerous.  -- Frank Herbert


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]