2021 LinuxQuestions.org Members Choice AwardsThis forum is for the 2021 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite projects/products of 2021. This is your chance to be heard! Voting ends on February 15th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Micro seems a cool replacement to nano, but the Ubuntu repo version apparently was compiled in debug mode, so micro ends up creating log files everywhere you run it. Any distro that uses the Ubuntu repo is affected by this.
When I think of a text editor, I think of operating in terminal (mode). If I am operating in a gui, I think of something in the gui line. Hence, this year, thinking cli, I choose my default goto nano.
Using Emacs, the need for CLI editor starts to be less obvious. Emacs offers remote editing capability : I edit any file in any machine/user (given ssh access) within my local Emacs.
Last edited by bodiccea; 02-11-2022 at 04:02 PM.
Reason: more precisions about tramp
Distribution: openSUSE, Raspbian, Slackware. Older: Coherent, MacOS, Red Hat, Big Iron IXs: AIX, Solaris, Tru64
Posts: 2,741
Rep:
An oldy but goody: Emacs
Learned the keyboard navigation from Perfect Writer that came with my CDP XT clone back in the day. My documentation workflow has, for a long time, involved a shell script that creates a skeleton LaTeX file based on the title of the doc and an include file for "make", runs it through 'latex' to create a PDF and, then, launches Emacs naming the new (or existing) ".tex" file, doing the the same for the Okular with the ".pdf" file. Running "make 'blah.pdf' and up-arrow-<return>" in the terminal is all I need to update the Okular display. Little of this requires moving hands from the keyboard.
I've been experimenting with VSCode and a few plugins that support TeX/LaTex files. The new workflow is a little different: it'll update the ".dvi" file automagically (viewable in another VSCode tab) upon saving the ".tex" file. (It doesn't yet create the make include file I'd need for easily making PDFs but that is probably fixable). At his point I'm unsure if that combination is enough to supplant my Emacs-based process.
Now if VSCode ever discovers the beauty of the expression highlighting option for parentheses/brace/bracket matching... (The VSCode's 'Blockman' plugin is interesting but ju-u-ust doesn't quite do it.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.