Vis: A Vim-Like Text Editor
github.com
Vis: A Vim-Like Text Editor
1–10 of 166 posts
Re: Vis: A Vim-Like Text Editor
#2Re: Vis: A Vim-Like Text Editor
#3Re: Vis: A Vim-Like Text Editor
#4Re: Vis: A Vim-Like Text Editor
#5Looks promising, and support for huge files is a weak point in vim, so I gave it a try. My usual workflow with big logfiles is to zoom into certain types of messages with e.g. :v/error/d and back out with u, and alternatively jump from one occurrence of a string to the next with *. That doesn't seem to work, so for the moment it's not the right 80% for me. But I do think it's a worthy project, so I'll keep an eye on…
Re: Vis: A Vim-Like Text Editor
#6But what does it got that vim doesn't?
Re: Vis: A Vim-Like Text Editor
#7That video needs sound, I have no idea about what's happening.
Re: Vis: A Vim-Like Text Editor
#8But what does it got that vim doesn't?
Re: Vis: A Vim-Like Text Editor
#9But what does it got that vim doesn't?
Two well-known editors to come from the ed tradition: vi and sam. Vi is an obvious evolution - make it 2d. Sam did this as well, but its main focus was developing the expression language. For example, so you can chain expressions together for text manipulation. Another comment mentions multiple cursors.
But sam also has plan9 culture. It strongly encourages the mouse with an interaction that I've found to difficult to adjust to.
Vis seems to unify the best bits of vi and sam, from a unix user's perspective.
If anyone reading this knows sam or vis fluently, it would be helpful to have a youtube video for each of sam and vis in the the style of the recent Russ Cox video on acme.
[I'm struggling to get this vis thing to build and run, tips? Debian stable. I downloaded libtermkey, configure, make make install. Not thrilled about this - would rather it create .a and .h files I could copy it into the vis dir. Now when I run ./vis it says, "error while loading shared libraries: libtermkey.so.1: cannot open shared object file: No such file or directory".]
Re: Vis: A Vim-Like Text Editor
#10Looks promising, and support for huge files is a weak point in vim, so I gave it a try. My usual workflow with big logfiles is to zoom into certain types of messages with e.g. :v/error/d and back out with u, and alternatively jump from one occurrence of a string to the next with *. That doesn't seem to work, so for the moment it's not the right 80% for me. But I do think it's a worthy project, so I'll keep an eye on…
What does :v do?