Run bashtop

[andychu]

This is over 5K lines of bash:

https://github.com/aristocratos/bashtop

$ wc -l bashtop 
5250 bashtop

After editing out the version check, we get some expected errors that are easily fixed (e.g. by editing quotes):

$ osh bashtop 
  declare -A graph_symbol_up='(
             ^~~~~~~~~~~~~~~~
bashtop:228: 'declare' Got -A but RHS isn't an associative array
  declare -A graph_symbol_down='(
             ^~~~~~~~~~~~~~~~~~
bashtop:235: 'declare' Got -A but RHS isn't an associative array
  box[boxes]="cpu mem net processes"
  ^~~~
bashtop:243: fatal: Associative array keys must be strings: $x 'x' "$x" etc.

[Crestwave]

Ah, I actually wanted to talk to you about how read is the current biggest blocker for running more programs; most of its flags are fundamental and cannot be worked around, and Bash TUI programs rely on them.

So of course, this does as well; I didn't do a comprehensive check on what it uses, but I'd rank the priority on -s, then -t, -u, -e, and -i. -N and -p could be worked around temporarily.

At least one of these flags is used in other TUI programs such as fff, pxltrm, birch, shmenu, etc.

[andychu]

OK thanks, it's good to know what's blocking testing.

• I looked at -s the other day, I think it should be easy
• -t is used by ble.sh (-t 0 is done)
• -e is used by mal lisp