st VS micro-editor

> you need to "edit your makefile". That isn't going to work for distributions

Is it not? [st] requires exactly that. And distros seem to have no issues shipping it.

[st] https://st.suckless.org/

I am fundamentally and ideologically opposed to using a terminal emulator implemented in electron.

If you feel similarly, then you might enjoy https://st.suckless.org/

You can use different forks of the ST. I, for example, use this one, already with the necessary patches https://github.com/mrdotx/st

kiss with kiss-xorg, nsxiv, st, dmenu with script, tewi, fet.sh

My journey of using terminal emulators began together with my introduction to Linux about 7 years ago. GNOME terminal was my first as it came pre-installed on Ubuntu, my first Linux distribution. Since then, I've had the opportunity to explore and utilize a range of terminal emulators, including Alacritty, Kitty, st, Konsole, xterm, and most recently iTerm2. It's been interesting to experiment with these different emulators, each offering its unique features (or similar however with each with personal touch), user interfaces, and performance benchmarks. Just the other day, a new terminal emulator caught my attention: Warp Terminal. My curiosity won, and Warp was downloaded, this short blog are my thoughts about Warp terminal. At the moment there is only support for macOS, however linux and windows builds are on the way.

Terminal : st

For those looking for a minimal VT100 terminal emulator without the legacy baggage of Xterm, I highly recommend checking out Suckless Software’s st: https://st.suckless.org/

That last reference builds off of the work of the other two. It also breaks down how NOT modern Xterm is, but, if I've read it correctly, it confirms that its input latency is low compared to all other tested terminal emulators, including Alacritty and ST, which humorously and justifiably thrashes Xterm on its homepage for being a bloated program. Its not a good choice for everyone: it has poor right-to-left text and Unicode support, making working with Chinese, Arabic, and other alphabets not great, I've read.

ST is a favorite of some fervent minimalists. I do not think you would like it.

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro