On 8/9/2019 7:38 AM, Bryan J Smith wrote: > Bradley D. Thornton <[email protected] <mailto:[email protected]>>
> To remain distribution agnostic as much as is possible, I would > contend that which $EDITOR is 'chosen' > > (and many distros default to nano) is more important an aspect than > which. > > > Humor me for a moment ... maybe it's all about the phrase 'many > distros'**? ;) Well, you got me there. The second or third thing I do following an install is make sure my default editor is set to Vim (or vi, temporarily), then my plugins later, after critical first configs. But that's me. And as you point out, the Alpine packages aren't even installed by default on SuSE or CentOS, IIRC. I only install that package because I use pine for local admin mail, or rather, Alpine, and alias it out. If the objective is to cover the editing of files, and the 'assumption' is that $EDITOR is set to nano, then, as you suggest, no time at all concerning the workings of an editor needs to be covered. I guess it's just easy for me to expect that one should know vi basics or know to use nano. More coverage can be focused on editing files and some of the pitfalls (like some config files that get weird with white space, etc.) if the effort isn't spent on the proficiency in one editing tool or another. If there *must* be some coverage of editor mechanics, then it most certainly should be vi (with ed receiving mention) and NOT nano, IMO ;) -- Bradley D. Thornton Manager Network Services http://NorthTech.US TEL: +1.310.421.8268 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
