Yasuhiro Matsumoto wrote: > > So we can just change :p to expand 8.3 names to their long name and > > that's it. > > Sorry for delay. > > https://gist.github.com/2832022 > > I wonder whether we should change :p behavior. I'm thinking there are > some cases to use "8.3". For example, 8.3 don't have spaces in the > path. So it's useful to avoid any bugs when executing external > program. > I applied this patch above, But some vim plugins occur error. That > beleave fnamemodify(tempname(), ':p') dont contains any spaces.
Well, I think plugins should be able to handle file names with spaces, as they occur quite frequently on MS-Windows. When I look at the documentation for GetLongPathName it mentions restrictions when using the ANSI version. We have the usual problems with 'encoding', thus we should use the wide version GetLongPathNameW when possible, with the encoding conversion when needed. Putting the function in os_win32.c would be appropriate, using GetFullPathNameW() is also there. > So I suggest one more another patch. > > https://gist.github.com/2831996 > > This is new modifier ":f". User can manually handing "8.3" path names. > If you allow this, I'll add patch for doc. We discussed this previously. I think it's simpler to use :p to get the full path and when someone needs the 8.3 name use :8 after that. No need for a new modifier. -- hundred-and-one symptoms of being an internet addict: 13. You refer to going to the bathroom as downloading. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
