3 ms·
Issues. 1. When I google for "nano ctags", I get one hit: someone's 2011-dated blog about their custom "nanotag.sh" which searches through the tags file and th
by kazinator 5y ago
Issues.
1. When I google for "nano ctags", I get one hit: someone's 2011-dated blog about their custom "nanotag.sh" which searches through the tags file and then runs the editor to bring up the right line of the right file, which is kind of like walking a quarter mile to get water from a well instead of having running water.
Maybe Ariadne uses nothing but cscope for naviating through code bases? Cscope is a bit crippling; you use it as a kind of dashboard for searches to which you have to return to start another search. If you find occurrences of an identifier, you have to return to cscope to navigate through that list.
2. I don't see any documented support for running a compile job out of Nano such that it gathers the errors and lets you move around in them for fixing.
3. No mention of "lisp" in the manual. How is the Lisp auto-indent and such?
Ariadne talks about getting the editor to "look" like Vim, but I don't see the point. What does that mean? Vim looks more or less like ... a section of your file. That's what you see. Plus some syntax coloring; is that the point? Looks are only skin-deep; the semantics is invisible from just looking at the editor screen.
She presents a falsely incomplete set alternatives ("false trichotomy"): it's either Vim, Emacs or Nano. It has to be Nano because Vim is modal and Emacs Lisp is yucky (complete with a meme about Emacs being an OS with a lousy editor) (so why would the author care that there appears to be no Lisp editing support in Nano, right?)
But, say, about good old Joe? Joe has ctags support and stepping through compiler errors and such. It's substantially more suitable for programming than Nano.
By my estimation, Joe could be the editor the author actually wants.
Another unexplored possibility is Jed.