Closed hachesilva closed 10 years ago
Ok. I'll check the encoding of the file now.
Did you save as UTF8 with BOM?
I've just pushed an update, can you try again please.
Yup, it is working fine now.
Awesome! Thanks @hachesilva :)
Okay, this is new to me. Why would a missing newline at the end of the line fail in ST2? Or was there a BOM at the beginning of the file that github just skipped in ther diff view?
1d744901f8373c4ba4d4331adb851edd881b2c73
@FichteFoll I don't think it will, however adding a new line was the only way I could get it to commit with the new encodings.
DESCRIPTION: Working with Windows 7, My Sublime Text 2 automatically updated InsertNums to the latest version. After closing and reopening Sublime, I got this error: Error trying to parse file: Expected value in C:\Users\MYUSERNAME\AppData\Roaming\Sublime Text 2\Packages\Insert Nums\Default (Windows).sublime-keymap:1:1
Opening the file in Mac OS X 10.8 I can see the file content being the keymaps for the plugin. But opening it in Windows 7 I can only see weird characters.
POSSIBLE SOLUTION: By opening the file in Mac and saving it with UTF-8 enconding (File / Save with encoding / UTF-8) seems to solve the problem.