Re: Why is TERM=vt100 on the console?

[maya%netbsd.org@localhost]

On Thu, Sep 13, 2018 at 06:31:48PM +0700, Robert Elz wrote:
>     Date:        Thu, 13 Sep 2018 12:55:44 +0200
>     From:        Martin Husemann <martin%duskware.de@localhost>
>     Message-ID:  <20180913105544.GB23747%mail.duskware.de@localhost>
> 
>   | On Thu, Sep 13, 2018 at 12:47:59PM +0200, Benny Siegert wrote:
>   | > export TERM=wsvt25
>   | > 
>   | > makes a number of console applications display colors.
>   | > 
>   | > Why is this not the default?
>   |
>   | It should be the default for newer installs, but it is not changed on
>   | updates.
> 
> And for why, vt100 is more likely to work than anything else that could
> be picked aside from "dumb" - including for serial consoles (not everyone
> uses a wscons, even on amd64 installs).
> 
> And also, most apps that use colours (terminal colours, where the supported
> choices are usually quite limited) are *ugly* and having them supressed
> is no loss at all!
> 
> kre
> 
> 

Gotta drop my pumpkin spice latte and show off my favourite terminal
program, the fish shell. It doesn't even work in vt100, I assume because
they thought nobody would be using it in 2018.

https://i.imgur.com/1R8Ae1j.png
- It's red because there's no 'l' command
- always suggesting an auto completion if it can, based on commands that
  start the same as my command in history, but greyed out
- if I use tab, it lets me scroll through the options listed.

Similarly, it has a really clever thing for things that tlook like paths
to be red if they don't exist.

I really like it because I also have it configured with a key binding ^T
to launch fzf, which stops the need to type long pathnames: it does a
fuzzy search of the path for similar executables, so if I want to edit:
work/MyPackage-1.2.3/src/actualfiles/filename.c
I can just do:
pkgvi ^T filename
and get something like this:
https://i.imgur.com/BEC7HRG.png

and it will save me all the work about caring about how deeply nested
pkgsrc files get.