Viewing profile — martanne

> Long-waited NetBSD support in CI would be awesome to be finished too. As the maintainer of the linked vis project, I can confirm that the provided SSH access to the CI environmen…

The Plan 9 manual pages and papers are probably a good starting point: http://man.cat-v.org/plan_9/ http://doc.cat-v.org/plan_9/4th_edition/papers/

> A terminal app that has terminal features doesn't violate any principles of simplicity. It still depends how these features are implemented. For example in dvtm scroll back histo…

> Adding tmux just to get scrollback goes against Unix philosophy. There are also simpler tools which can provide scrollback support. The whole Unix tty subsystem goes against the …

You can be sure that the Kakoune authors are familiar with vi(m). Having said that, if you like both vi(m) and the structural regular expression support of sam/acme you might be in…

These operations are already supported by using structural regular expressions. As an example x g/foo will select all lines containing foo. Similarly x v/foo will select all lines …

Thanks for the feedback! Yes syntax highlighting for large files is a hard issue. I'm not really aware of an accurate an high speed solution supporting editing operations in huge f…

A number of people expressed the need to edit large files. For the development of my own editor[0] I would be interested to know what kind of usage patterns most often occur. What …

Does somebody know how it compares to radare2?

As the main developer of an editor (vis) using a similar segmented data structure (a piece chain, similar to a rope, but storing the text junks in a double linked list, thus asympt…

How do you plan to encode binary data in your JSON-based protocol? Base64? This will only increase the overhead. While the human readability of JSON is nice, it has some serious fl…

Thanks for the hacking file, it is a good read for people like myself who are interested in text editor implementations. If time permits I will try delve a bit into the joe code ba…

Kakoune is a fine editor. Regarding vis, Lua is optional (you lose syntax highlighting though). libtermkey is a 3 file library and despite what the author claims it works, is usefu…

The nice thing about the pointer as mark thingy is that while the offset from the start of the file might change when something is inserted before it, the pointer will remain the s…

Some things are just more convenient/efficient to do in C. As an example the mark handling[1] used to represent cursors/selection relies on pointer arithmetic. Other things like th…

Yes the lack of binary packages is a known problem. The whole project is still somewhat in flux, feel free to contribute by filling a packaging request to your favorite distributio…

I agree there are a lot of interesting ideas in 9term/sam/acme and Oberon (which was the initial inspiration for the project). In the future I would like to experiment with integra…

> Does it build with LuaJIT? I'm not sure. I think a few Lua >= 5.2 dependencies have crept in, but it shouldn't be difficult to fix this if desired. LuaJIT's FFI is indeed very ni…

Yes from a design philosophy standpoint vis is closer to kakoune than {neo,}vim. The implementation is quite different though (no C++, no boost, no home grown scripting/extension/s…

Reposting an answer from a related thread. The main difference is that vis is written from scratch while neovim inherited an old and hard to maintain code base. This allows vis to …

Everything involving searching is currently probably very slow for large files, this is especially true for backward searches. The reason being that we currently rely on the regexp…

As the producer of the "video" (it is actually ASCII, you can copy paste stuff out of it) I agree, here is an annotated version: - x/pattern/ extracts stuff from the text, creates …

I'm not really familiar with the vim code base. From the little I've seen I'm astonished that people are actually willing to voluntarily work on it. Having said that, googling reve…

No the main difference is that vis is written from scratch while neovim inherited an old and hard to maintain code base. This allows vis to experiment with various ideas: - native …

Yes vipe is indeed useful for editors which do not support it by themselves. Personally I find a solution solely based on pipes without temporary files more elegant. I should proba…