martanne

5 ms·

1.
by martanne 6y ago
> 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 environment is very convenient and saves a lot of time. I would als
2.
by martanne 10y ago
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/
3.
by martanne 10y ago
> 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 history is made searchable by piping it to $PAGER. Simila
4.
by martanne 10y ago
> 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 "Unix philosophy", that is why it was completel
5.
by martanne 10y ago
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 interested in vis which combines the two: https:/&#
6.
by martanne 10y ago
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 not containing foo. Sorting et
7.
by martanne 10y ago
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 files. In principle the underlying data structure used b
8.
by martanne 10y ago
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 are the most important operations? Do you search for some (r
9.
by martanne 10y ago
Does somebody know how it compares to radare2?
10.
by martanne 10y ago
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 asymptotically worse) I can attest that the performance is general
11.
by martanne 10y ago
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 flaws when the goal is to handle arbitrary data. I have yet to
12.
by martanne 10y ago
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 base. As for the syntax highlighting in vis, yes it currently
13.
by martanne 10y ago
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 useful and could be maintained in the vis repository if necessary
14.
by martanne 10y ago
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 same. Anyway this was just an example. I agree that higher le
15.
by martanne 10y ago
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 the syntax highlighting are implemented in Lua which
16.
by martanne 10y ago
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 distribution ... Historically it originates from a community which is c
17.
by martanne 10y ago
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 integrating a few more, but unfortunately time is a limit
18.
by martanne 10y ago
> 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 nice, but it is unfortunate that Lua has
19.
by martanne 10y ago
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/syntax highlighting language).
20.
by martanne 10y ago
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 experiment with various ideas: - native multiple cursors&#x2
21.
by martanne 10y ago
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 engine of libc and thus have to copy the underlying text to
22.
by martanne 10y ago
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 a selection for every match -
23.
by martanne 10y ago
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 revealed a bug report[1] where one of the main ne
24.
by martanne 10y ago
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 multiple cursors/selection support - structural regular
25.
by martanne 10y ago
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 probably let dvtm fall back to vipe if it is installed. Also I wi
26.
by martanne 10y ago
Vim is actually a relatively bad filter (some reasons are mentioned in the caveats section of the article). I explicitly designed my vis editor[1] in such a way that it can be used as an interactive filter. The following works as expected,
27.
by martanne 10y ago
Well technically you could inline the Javascript+CSS stuff and you would get a single HTML file ;) No need to write anything, it already exists. Anyway I didn't mean to discourage you from working on your project. I just would like to
28.
by martanne 10y ago
asciinema stores the raw program output including any terminal escape sequences in a JSON format[1] and then uses a javascript terminal emulation library to replay/recreate the terminal state in your browser. The player, made up of one
29.
by martanne 10y ago
asciinema[1] does a similar thing but captures a whole terminal session. If somebody would add key input overlay support[2], it would actually be tremendously useful for demonstration purposes of interactive, mainly keyboard driven, termina
30.
by martanne 11y ago
As the primary author of these tools, please report core dumps/stack traces of the crashes (if you get hold of them). At least for my use cases, the current git versions seem to be stable ... Having said that, if I ever find the time I

More ›