Le samedi 13 décembre 2014 23:24:14 UTC+1, Christian Brabandt a écrit : > Hi Enno! > > On Sa, 13 Dez 2014, Enno wrote: > > > To use Vim under powershell in MS Windows, set &shell=powershell and > > &shellcmdflag=-c. > > > > However, if &shell=powershell and &shellcmdflag=-c, then tempname() returns > > a file name with forward slashes because 'powershell' contains 'sh' and > > '-c' starts with '-'. > > > > Then again, if instead &shellcmdflag=\ -c, that is, a leading space is > > added, then tempname() uses backward slashes. > > > > Because powershell expects backward slashes, the second setup is better but > > also less intuitive. How about a note in the documentation of &shellcmdflag? > > Have you tried unsetting the shellslash option? That should create a > tempname with backslashes, if I read the documentation correctly. > > Best, > Christian > -- > Schreit die Ente "wuli, wuli", ist es Märzen oder Juli.
Hello Christian, shellslash is unset (it would force forward slashes). The problem is that Vim assumes that every shell that contains 'sh' and takes a cmdflag starting with '-' is a posix compatible one. Best wishes Enno -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
