Closed konyahin closed 1 year ago
It may not be backward-compatible to let ex
(nvi's cmdline core or scripting language) interpret characters differently, but making special characters more readable and editable is possible. If you like that approach, you can look at how the code displays \uXXXX
Unicode escape sequences. The end effect will be displaying U+001B as <Esc>
, a five-character wide glyph, but it is treated as one character when editing.
@konyahin nvi2 already does a pretty good job of displaying non-printable characters but, if you'd like to view them oursite of nvi, then just use vis(1)
as this is precisely its job.
Thank your @lichray I will think in this direction. @rjc maybe I will happy with it, thank you.
Hello. I like nvi2 and I like ability to make my own maps with shell integration. It allows me to doing cool stuff, like
But I be needed to use unprintable special characters, if I want to use enter, or escape. So my maps become unreadable and unmaintainable. In big brother we can do something like that:
I looked at source code and now I have working prototype of patch with this stuff. But before I will make boring work (documentation, new option and code cleaning), I want to ask you, do you see things like this in nvi? Will you accept my PR, or it to much for nvi?