-
Notifications
You must be signed in to change notification settings - Fork 455
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
Prompt color in terminal inside vim changes #224
Comments
I'm not altogether surprised. Getting terminal_ansi_colors to play nicely with term and everything else is not always straightforward. Do you have a terminfo compiled for alacritty? Here's mine:
I also have this hack in my vimrc to get if $TERM =~# '\v(tmux-256color)|(alacritty)'
" so colors work properly in :term, because apparently vim will default to
" `xterm` for :term when 'term' doesn't start with xterm...
"
" Phew. Glad that sentence is terminated.
set term=xterm-256color
endif |
Thanks for the quick reply! I tried putting your $TERM hack into my .vimrc, but it had no effect.
|
What is |
:set term
let g:terminal_ansi_colors
I will try to user your terminfo files alongside with your .vimrc hack later when I get back from work. |
Given the lack of response, I'll close this. If still an issue, let us know. |
What happened
When the colorscheme is active and I launch a terminal inside vim (via :terminal), the colors of the bash prompt are different from what I have set in .bashrc. Sometimes it changes them to the dracula colors (pink and yellow) and sometimes it is just plain white.
What I expected to happen
The shell prompt inside vim should not differ from the one in any other terminal (emulator).
Screenshot
My standard bash prompt (outside vim):
The shell promt in a terminal inside vim:
Machine Info
vim
/gvim
/neovim
): vimTERM
environment variable: alacrittyI have also tried setting the $TERM variable to diferent values like xterm-256color or tmux-256color. The results are the same.
Additional Info
The same thing happens on my Artix system, so the problem also occurs on precompiled versions of vim and is not specific to my self-compiled vim on gentoo.
The text was updated successfully, but these errors were encountered: