gdu VS micro-editor

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

For anyone that likes ncdu I would highly recommend gdu. https://github.com/dundee/gdu

gdu is faster

gdu - Just a very fast and cool disk usage explorer

The RPCS3 flatpak lives in /home/deck/.var/app/net.rpcs3.RPCS3. I'd advise you to install a tool like gdu or use something like du -h --max-depth=1 in the console in that directory, to find where the disk usage goes. There are also GUI tools, but I prefer these myself.

While ncdu does the job I've found gdu (similar tool written in Go) significantly faster for larger directories.

https://github.com/dundee/gdu

There's also gdu, which is much faster on SSDs.

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

I am all for your efforts.

I am very keyboard centric. My sweet spot is macOS keyboard shortcuts. Especially those as defined by BBEdit.

But I have learned from all the platforms I have worked on. (TRS-DOS, MSDOS, OS/2, macOS, Windows, Linux)

I never get into Vim primarily because of HJKL. I have spent many hours trying. But I do use IJKL as arrow keys via hardware keyboard macros, AutoHotKey, Karabiner Elements, or the like. I have mostly bent Windows and KDE Linux to my Mac-like keyboard standards. (And my Mac’s are heavily customized too)

I do heavily use CTRL and arrow keys for word by word navigation, and all the other arrow key bindings. So that is a personal deal breaker for me.

You should take a look at the Micro editor. It shares many of your ideas.

https://micro-editor.github.io

I would like to follow your work. Please post a link to a blog or git repository