Chris's Wiki :: blog/unix/VimNowAUser Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/VimNowAUser?atomcommentsDWiki2020-09-20T21:28:37ZRecent comments in Chris's Wiki :: blog/unix/VimNowAUser.By rjc on /blog/unix/VimNowAUsertag:CSpace:blog/unix/VimNowAUser:788d2f2411b8945b34e6eb72978c9a247c8059ffrjc<div class="wikitext"><p>@David I couldn't agree more - first, well the second (after installing <code>etckeeper</code>), thing I do on Ubuntu is to install <code>nvi</code> and make sure the <code>editor</code> and <code>vi</code> alternatives point to it. The same goes for <code>ex</code> and <code>view</code>. By <em>I</em>, I obviously mean the config management systems ;^)</p>
<p>Fortunately, on <em>OpenBSD</em> I don't have to do anything as <code>nvi</code> is the default <code>vi(1)</code> :^)</p>
</div>2020-09-20T21:28:37ZBy P Kern on /blog/unix/VimNowAUsertag:CSpace:blog/unix/VimNowAUser:796497fe5bae0587e085c8df1287f3e46f66c6bbP Kern<div class="wikitext"><p>Thanks David Magda.
I was afraid I might be the only "cranky old guy" still plugging away.</p>
</div>2020-09-17T16:19:15ZBy Kevin Lyda on /blog/unix/VimNowAUsertag:CSpace:blog/unix/VimNowAUser:543d5c2687b5a1d7f74d804377668414ee9062bfKevin Lydahttps://phrye.com/<div class="wikitext"><p>A vim plugin you might look into is the Asynchronous Linter Engine (<a href="https://github.com/dense-analysis/ale">ALE</a>). I code in a number of languages and ALE catches a number of silly style and syntax errors.</p>
<p>Used with things like <a href="https://www.shellcheck.net/">shellcheck</a>, pylint, go's lint tools, php checkers and so on, it's really handy at squashing a lot of the sillier errors.</p>
</div>2020-09-14T15:42:35ZBy David Magda on /blog/unix/VimNowAUsertag:CSpace:blog/unix/VimNowAUser:a04f0d6333c499c9e55f0d7b8508068ed03b3b6aDavid Magdahttp://www.magda.ca/<div class="wikitext"><p>One of my pet peeves is that by default on a lot of Linux systems when you type in "<code>vi</code>" you actually get Vim. You can tell this is the case by the fact the file is colour/syntax-highlighted. </p>
<p>I'm sure this is a useful if you're writing code all day, but when you simply want to make a tweak to your <code>.bashrc</code> or <code>my.cnf</code>, then it's really distracting. If I wanted Vim I would have typed in "<code>vim</code>", thank you very much.</p>
<p>See also the default of having the output of "<code>ls</code>" colourized: thanks, but I have no idea what 'blue' means, especially in a multi-platform, heterogeneous environment. But I know, when running "<code>ls -F</code>", that a "/" at the end of an item means it's a directory.</p>
</div>2020-09-14T12:06:34Z