On Tue, Jul 24, 2018 at 4:17 AM alphaCTzo7G <[email protected]> wrote:
> @lilydjwg <https://github.com/lilydjwg> .. actually not sure if its a > problem with Universal ctags, (compiled a few days back.) there seems to be > multiple issues here.. One was with the python-api.. > > I thought what I posted above was related but it seems the issue in this > image > [image: image] > <https://user-images.githubusercontent.com/29691914/43110872-305860be-8ea3-11e8-99b1-5c4a747bd40d.png> > > is related to the terminal I use (Putty), but is also present in Kitty, > MobaXterm, BitVise ssh client as well tmux/tmux#1409 (comment) > <https://github.com/tmux/tmux/issues/1409#issuecomment-406852634> > > If I try this in Gvim, or use a different terminal such as Gnome-terminal, > or rxvt-unicode that has unicode support, this issue in the above image > doesn't happen. So I will probably have to report these to them > (Putty/Kitty etc).. Its not too much of a issue.. and probably a edge case, > so maybe thats why they haven't bothered to fix it. > > vim.eval still breaks for the 3 files I posted regardless of what > terminal I use or if I use Gvim.. > `vim.bindeval` always uses `bytes` in place of `str` regardless of `&encoding` and Python version, so you can always choose what you to do with non-UTF-8 text. Though it is not without issues (or features which may cause issues): - For each container (list, dictionary) it will return not Python’s `list` or `dict`, but a binding to the container. That may need to be converted depending on where you pass that container. - `bytes` is harder to use in Python 3 as they are no longer meant to be text strings. You probably just not *can* choose in this case, but *must* choose each time. - Since Python is in external process in Neovim naturally Neovim does not support `bindeval`. (And should it support each access would invoke IPC which directly opposes the initial reason of `bindeval` existence - to make certain code faster.) > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/vim/vim/issues/3213#issuecomment-407248767> > > -- > -- > 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. > -- -- 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.
