Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 371 by ch...@chrullrich.net: Windows: If file name on command
line starts with space, preceding backslash is lost
https://code.google.com/p/vim/issues/detail?id=371
What steps will reproduce the problem?
1. Create a file named " testfile.txt" (leading space).
2. Start Vim and pass the file name on the command line, including at least
one
parent directory (i.e. gvim.exe "test\ testfile.txt")
What is the expected output? What do you see instead?
I would expect Vim to open the file. Instead, it swallows the backslash
before the space and opens "test testfile.txt" as a new file.
What version of the product are you using? On what operating system?
7.4.711 (Cream vanilla), Windows 8.1
Please provide any additional information below.
The same effect occurs when using the shell context menu. The bug is in
Vim, see below:
C:\test>py -3 -c "import sys; print(str(sys.argv))" "test\ testfile.txt"
['-c', 'test\\ testfile.txt']
Python does not lose the backslash.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
