Description
fish shell >=4.1 assumes terminals implement Primary Device Attribute, see the "Required Commands" table at https://fishshell.com/docs/current/terminal-compatibility.html
In micro, if I do ctrl-e term enter, and then run
bash$ printf '\033[0c'; cat -v
I see no output, which shows that micro's terminal does not send the Primary Device Attribute.
This is a reason why fish shows an error and some startup delay.
Another bug that causes breakage OOTB withfish is that micro's term interprets printf '\033[=u' as "move cursor to the top left". This is wrong; only printf '\033[u' should do that (i.e. if no private mode = byte was specified).
Originally reported at https://www.reddit.com/r/fishshell/comments/1s0sgv7/problem_opening_terminal_inside_micro/
Description
fish shell >=4.1 assumes terminals implement Primary Device Attribute, see the "Required Commands" table at https://fishshell.com/docs/current/terminal-compatibility.html
In micro, if I do
ctrl-etermenter, and then runbash$ printf '\033[0c'; cat -vI see no output, which shows that micro's terminal does not send the Primary Device Attribute.
This is a reason why fish shows an error and some startup delay.
Another bug that causes breakage OOTB withfish is that micro's
terminterpretsprintf '\033[=u'as "move cursor to the top left". This is wrong; onlyprintf '\033[u'should do that (i.e. if no private mode=byte was specified).Originally reported at https://www.reddit.com/r/fishshell/comments/1s0sgv7/problem_opening_terminal_inside_micro/