vis: always store registers values NUL terminated

Previously we only made sure that the register content is NUL terminated
when reading it out. This made it impossible to distinguish between an
empty register and one which stores a single NUL byte. Now the in memory
representation of a non-empty register is always NUL terminated. When
appending we temporarily remove the trailing NUL byte and restore
it later.

This should fix put commands of a previously yanked single NUL byte.

0 files changed, 0 insertions, 0 deletions