-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add default terminal implementation #5199
Conversation
I am not sure how much |
That's a good point, I made another change to ensure we have '$TERM' exists using |
Do alacritty or Terminal.app even set $TERM to something that could be used to launch them? My understanding is that most terminals set $TERM to "xterm" or "xterm-256color" for compatibility reasons, regardless of what the terminal's actual name is. |
I tested, alacritty works as it set TERM to 'alacritty', and some others also works based on http://jdebp.uk./Softwares/nosh/guide/TERM.html , of course there are still a lot of others don't work. In this patch, I added this to the last to only give it a try if none of others doesn't work. |
@mawww , @Screwtapello , do you think using
|
don't figure out a good way, let's close it for now |
here is the logic from neofetch, it looks like complex.
|
it seems that most of terminal support
-e
option, let use it as a fallback implementation so that we can useterminal
andnew
on other undefined terminal like alacritty, Terminal.app.