5 ms·
I just ignore the entire TeX-Editor landscape and use VSCode with LaTeX Workshop. The latter falls apart for what I use it for often (*.cls files etc.), but VSC
by diarrhea 5y ago
I just ignore the entire TeX-Editor landscape and use VSCode with LaTeX Workshop. The latter falls apart for what I use it for often (*.cls files etc.), but VSCode is simply so much more powerful than any niche, language-specific editor can ever hope to be.
LaTeX-specific support like tab completion mentioned in this thread ("hit a+tab for alpha") also doesn't work in my use cases. I use `glossaries-extra` for everything it's suitable for, so all symbols are glossary macros and not literal letters (`\alpha`...). It makes the source beautifully readable and is more in LaTeX's spirit: what you mean is what you get (`\section` vs. `\large\bfseries\sffamily`...). So instead of `\alpha` it might say `\sym{absorbtion_coefficient}`. If you ignore the necessary `\sym` macro bit, equations in source code will read like you'd say them out loud. There's no ambiguity left, what the author meant is right there, no guessing needed.
Want to change the symbol? There's only one place you'll have to change it at. Often, you cannot change e.g. `\alpha` globally (sed and friends) because such a popular symbol is probably used in multiple contexts.
Generate a nomenclature? It's one command once everything is set up, no manual `nomencl` (which is an awful, hacky, old thing) sorcery anymore. You can even print a list of all the pages a symbol, acronym, ... has been used.
And that's just `glossaries-extra`. There's `unicode-math`/`fontspec`, `tcolorbox`, `polyglossia`, `csquotes` (latex editors might helpfully auto-complete quotes (``''), but that is entirely misguided in the first place; use `csquotes`), `cleveref`, `biblatex`, `floatrow`, `caption`, ... modern LaTeX is pretty wonderful and has a lot to offer, but I found LaTeX-specific editors lag behind and their LaTeX-specific support is not useful in a lot of those cases. Plus, LaTeX Workshop is very good in its own right.
- GiovanniP 5y ago> I just ignore the entire TeX-Editor landscape TeXmacs is not a TeX-editor, it is an independent program. The word "TeX" is in the name because one of the ambitions of the program is to inherit the typographic excellence of TeX (see the "parent article"). On this topic, the author of TeXmacs claims he has surpassed it.
- taeric 5y agoIt is rather amusing how this product is neither TeX, nor emacs. Pretty sure the vast majority of folks assume it is related to at least one, if not both.
- GiovanniP 5y agoAccording to Joris van der Hoeven "... it has become clear over time that this choice of name was one of the biggest mistakes of the project. Indeed, the name incorrectly suggests that TeXmacs is some kind of interface to (La)TeX."
- forgotpwd16 5y agoBesides that TeXmacs isn't a TeX editor, how exactly is VS Code more powerful than TeXmaker for example for the purpose of authoring TeX documents?