I would boot up the computer with a Linux disk and use linux to change the filenames.
Gerald Klein DBA
ContactMe@geraldklein.com
www.geraldklein.com
geraldklein.wordpress.com
jk@zognet.com
708-599-0352
Arch/Gentoo Awesome, Ranger & Vim the coding triple threat.
Linux registered user #548580
ContactMe@geraldklein.com
www.geraldklein.com
geraldklein.wordpress.com
jk@zognet.com
708-599-0352
Arch/Gentoo Awesome, Ranger & Vim the coding triple threat.
Linux registered user #548580
From: David Balažic
Sent: Wednesday, March 19, 2014 9:45 AM
To: vim_use@googlegroups.com
Sent: Wednesday, March 19, 2014 9:45 AM
To: vim_use@googlegroups.com
I used vim 7.3 and from today 7.4 on Windows 7 Pro SP1 64 bit.
It seems it has problems opening files that have non-ascii characters in their names.
For example:
- I create file named testčšž.txt (in case this gets corrupted, that is testcsz.txt with caron on the c, s and z)
- in Windows Explorer I right click the file and choose "Edit with Vim"
Expected: the file is opened in GVIM
Actual:
- a new file is created/opened in GVIM
The GVIM window title says testcšž.txt for filename (the č lost the caron),
also the bottom of the window says:
"C:\path\testcXX.txt" [New File]
X are black squares
So:
- the 'č' gets converted to 'c'
- 'šž' is displayed correctly in windows title, but in the status line
I put a screenshot here: http://imgur.com/NNtUuxl
If I save this file, a file named "testcšž.txt" is created.
It is also the same if I drag'n drop the file into a running GVIM window.
Is this a known issue or some misconfiguration?
Regards,
David Balažic
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment