Lilydjwg wrote: > The previous python3 patch fixed Vim's python3 unicode errors when there > are no errors. But when there are invalid characters in the buffer, > exceptions may be raised by python, but vim only prints a warning in > that situation. And in python 3.1 and later, invalid characters from > file names and environment variables are handled using an error handler > called 'surrogateescape'.[1] I think Vim should do like this and don't > break the gundo plugin I'm using. > > To see the errors, open the attached 'test' file in UTF-8 encoding > (vim should say there are invalid characters) and try execute: > > py3 import vim > py3 vim.current.buffer.append(vim.current.buffer[0]) > > With the patch applied, there will be no errors and two same line. > > Anyway, when outputing invalid characters, unicode errors are still > raised. This is the same behaviour with the interpreter. > > [1]: http://www.python.org/dev/peps/pep-0383/
Thanks. I'll add it to the todo list. -- hundred-and-one symptoms of being an internet addict: 204. You're being audited because you mailed your tax return to the IRC. /// 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
