Forgot your password?
typodupeerror

Comment Continuing on Acme, Emacs, etc. (Score 1) 286

I was once inspired by https://doc.cat-v.org/plan_9/1st_edition/help/help.pdf and started writing my own "modern" take on it at https://github.com/tleino/vtsh . I also implemented support for Sixels (not published in 'vtsh'), so that I could 'cat' an image.

I think it is a bit boring to have an infinite scroll that combines input and output to the same buffer, without any way to structure it and separate the input from the output, so that you could group the chunks of output based on the given input, so that you could do things like close chunks of output, edit the chunks of output, scroll individual chunks of output, resubmit the chunks of output to an another command, etc. In the end what you'll get will become a very nice editor like Emacs or Acme. Or then you could simply use the terminal emulator as an terminal emulator, and an editor as an editor and image viewer as an image viewer and use the window manager as a way to combine the tools, and there would be also a very good logical separation, and what you get is programs optimized for its job.

Nowadays I simply use https://github.com/tleino/mxswm window manager for efficient multi-tasking (or I could continue the development on https://github.com/tleino/cocowm ) and using programs that are optimized for their purpose.

The advanced terminal emulator, 'vtsh', that I tried to develop ended up (at least for now) being a nice experiment where I was able to toy with the idea that I can get fullscreen editing to the 'ed' line-editor without touching a line of 'ed' source code, which was fun, even though the 'vtsh' is an editor in itself (because of the editable output buffers) and can be used without 'ed'.

Finding the perfect compromise on power, simplicity and composability is intriguing.

Slashdot Top Deals

The universe does not have laws -- it has habits, and habits can be broken.

Working...