Re: resolve() on Windows breaking change

2019-06-06 Fir de Conversatie Mike Williams
Hi Ken On 05/06/2019 11:56, Ken Takata wrote: > Hi, > > 2019/6/5 Wed 5:25:13 UTC+9 Mike Williams wrote: >> On 04/06/2019 19:18, Bram Moolenaar wrote: >>> >>> Mike Williams wrote: >>> It looks like the change to Windows for resolve() in 8.1.1417 was a breaking change. I use the

Re: resolve() on Windows breaking change

2019-06-05 Fir de Conversatie Ken Takata
Hi, 2019/6/5 Wed 5:25:13 UTC+9 Mike Williams wrote: > On 04/06/2019 19:18, Bram Moolenaar wrote: > > > > Mike Williams wrote: > > > >> It looks like the change to Windows for resolve() in 8.1.1417 was a > >> breaking change. I use the NERDtree plugin and any build after than > >> change

Re: resolve() on Windows breaking change

2019-06-04 Fir de Conversatie Mike Williams
On 04/06/2019 19:18, Bram Moolenaar wrote: > > Mike Williams wrote: > >> It looks like the change to Windows for resolve() in 8.1.1417 was a >> breaking change. I use the NERDtree plugin and any build after than >> change results in NERDtree reports plain files on Windows as links. See >>

Re: resolve() on Windows breaking change

2019-06-04 Fir de Conversatie Bram Moolenaar
Mike Williams wrote: > It looks like the change to Windows for resolve() in 8.1.1417 was a > breaking change. I use the NERDtree plugin and any build after than > change results in NERDtree reports plain files on Windows as links. See > attached image. > > I guess the question is. is this

resolve() on Windows breaking change

2019-06-04 Fir de Conversatie Mike Williams
Hi, It looks like the change to Windows for resolve() in 8.1.1417 was a breaking change. I use the NERDtree plugin and any build after than change results in NERDtree reports plain files on Windows as links. See attached image. I guess the question is. is this wrong in VIM or a bad assumption