2016-07-13 11:56 GMT+03:00 Rafal <[email protected]>: > I don't see any special characters as you do, to test that I'm running: >
They are from `hilite` program as I said. You would see them if 1. Some of the messages will contain multibyte characters (yes, Vim does not even write one character with one call, it uses one call per byte). This is essential because bug I see is due to parts of multibyte characters being followed by <Esc>. Outputting single-byte characters even byte-by-byte is not going to cause any problems. 2. Vim is run like `hilite ex …`. Though the purpose of this command is to be run on shell: I have `exec hilite $ZSH` in my `.zshrc`. “Hilite” is http://sourceforge.net/projects/hilite, portage description is “A utility which highlights stderr text in red”. It has some downsides though: some interactive apps think that they are running in a pipe if stderr is not connected to a tty, so I have alias -g T='&>/dev/tty' and can run such apps like `bash T` (though specifically bash is fine with forcing interactive mode using `-i` without reconnecting its stderr to tty). > ex -scq! -V1 /etc/hosts | cat -v > > which should show any non-printing characters. > > But I can confirm, running under debugger (dtruss in my case), I see each > character in each line, e.g. > > $ sudo dtruss -f ex -scq! -V1 /etc/hosts > .... > write_nocancel(0x2, "\r\n\0", 0x2) > write_nocancel(0x2, "\"\0", 0x1) > write_nocancel(0x2, "/\0", 0x1) > write_nocancel(0x2, "e\0", 0x1) > write_nocancel(0x2, "t\0", 0x1) > write_nocancel(0x2, "c\0", 0x1) > write_nocancel(0x2, "/\0", 0x1) > write_nocancel(0x2, "h\0", 0x1) > write_nocancel(0x2, "o\0", 0x1) > write_nocancel(0x2, "s\0", 0x1) > write_nocancel(0x2, "t\0", 0x1) > write_nocancel(0x2, "s\0", 0x1) > write_nocancel(0x2, "\"\0", 0x1) > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/vim/vim/issues/919#issuecomment-232297264>, . > > -- > -- > 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.
