> Unlike emacs or vim or even nano, it didn't have a bunch of invisible shortcut keys, just a Windows-like drop-down menu system (but rendered in DOS). You might like "joe", which was inspired by WordStar: . - Source: Hacker News / about 1 month ago

I actually have a bound set for WordStar 4. If you want to use something similar on modern systems, try "Joe's Own Editor." https://joe-editor.sourceforge.io/. - Source: Hacker News / 8 months ago

JOE is pretty nice https://joe-editor.sourceforge.io/ — a hybrid of WordStar and Emacs, and if you run it with `jstar` you get a pretty authentic WordStar experience which also reminds of the earliest Borland Turbo IDEs. - Source: Hacker News / 10 months ago

If you want to change your workflow, you might consider using a terminal based text editor though. There are many out there, the most famous being vi or emacs (though both a bit hard to use) and packages specifically for word processing exist as well (for example https://joe-editor.sourceforge.io/). It will need more getting used to, but this will pretty much run on a potato and you could use a pi zero or any... Source: over 1 year ago

JOE [1] has worked this way as long as I remember (which is close to 20 years). [1] https://joe-editor.sourceforge.io/. - Source: Hacker News / over 1 year ago

This is great! I used to install micro[0] as "nano with better shortcuts", but it was always a bit of an overkill, so I'm really happy with this change. One quirk that remains: even with --modernbindings, Ctrl+X and Ctrl+C will add to nano's clipboard, instead of replacing whatever is there. [0] https://micro-editor.github.io. - Source: Hacker News / 14 days ago

Is Micro[0] not a better, more purpose-fit solution to these issues? (Syntax highlighting quality, etc) Prev discussed: https://news.ycombinator.com/item?id=37171294. - Source: Hacker News / 5 months ago

To see more screenshots of micro, showcasing some of the default color schemes, see here. - Source: dev.to / over 1 year ago

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... - Source: dev.to / 6 months ago

I really like micro, a nano-like editor with a very sane, regular people friendly keybinding. Source: 6 months ago