I maintain enough vi skill to be able to open and save documents,
navigate around and make changes. One needs to understand command and
insert modes and minimally :q! and ZZ. There are multiple cheat sheets
available (e.g. a two page PDF at
http://www.atmos.albany.edu/daes/atmclasses/atm350/vi_cheat_sheet.pdf).
As long as nothing else is as universally distributed with a basic Linux
setup, we need vi skills - love vi or hate it.
Ian Shields
On 8/7/2019 7:39 AM, G. Matthew Rice wrote:
On Wed, Aug 7, 2019 at 5:21 AM Simone Piccardi <[email protected]
<mailto:[email protected]>> wrote:
As we are discussing, this seems to me more and more a rite of
passage.
And not in the sense of a common knowledge shared by people, but
like an
initiation to be part of the sect of the "vi only editing" sysadmin.
Perhaps it comes down to your environment. When I control it, I have
everything I want. When I'm out consulting, that control is gone. In
those cases, I view vi as a tool of last resort....and one I have to
resort to often. And it sure beats editing config files with sed or ed.
Sure, containers are changing this dynamic but they aren't ubiquitous
yet. I think Bryan's onto something with the break-fix vs rebuild-fix
idea, too. In that regard, the two most commonly requested additions
to the objectives are more security and more troubleshooting (aka
break-fix?). The latter of which may or may not include text editing.
--matt
--
G. Matthew Rice <[email protected] <mailto:[email protected]>> gpg id:
0x17CF9077
Executive Director, Linux Professional Institute
_______________________________________________
lpi-examdev mailing list
[email protected]
https://list.lpi.org/mailman/listinfo/lpi-examdev
_______________________________________________
lpi-examdev mailing list
[email protected]
https://list.lpi.org/mailman/listinfo/lpi-examdev
