Errors on NUL characters in vroom files. about vroom HOT 4 OPEN

It needs to be something --remote-send can accept. At least <Nul> should work, but looks like it doesn't, either:

  % ab<Nul>cd
  ab^@cd

FAILED on line 1: Suspected error message:
E29: No inserted text yet

Message was "E29: No inserted text yet"

Failed command on line 1:
% ab<Nul>cd

Last few commands (most recent last) were:
iab<Nul>cd<ESC>

The exception and behavior you're seeing are a little surprising, too. There's probably some overall bugginess with special characters. Not sure if we actually want to support literal NUL characters, but if not we could at least improve the error message to say Unsupported character "^@". Use "<Nul>" instead..

from vroom.

Quick check for Neovim's replace_termcodes is turning 'ab\x0cd' into 'ab' not sure why. It is quite possible it is not ready to take a Null byte.

As for the and cases it is likely they are affected by #36(neovim/neovim#1270)

from vroom.

Quick check for Neovim's replace_termcodes is turning 'ab\x0cd' into 'ab' not sure why.

Because replace_termcodes() doesn't take a len parameter (needs to return one, too) and relies on strlen(). Same for ins_typebuf(). The String object we pass to it does have a len member, so it should be trivial to fix. Would it be too non-topical to add that change to neovim/neovim#1270?

from vroom.

Quick check for Neovim's replace_termcodes is turning 'ab\x0cd' into 'ab' not sure why.

Actually, it's working for the lua tests (neovim/neovim#1296 (comment)), but it converts NULs to newlines within the line. We just need to modify the API (buffer_get_*) to convert them back.

from vroom.