[vim/vim] Colors changing upon first action? (Issue #16649)

25 views
Skip to first unread message

shield29384

unread,
Feb 15, 2025, 11:58:46 PM2/15/25
to vim/vim, Subscribed

Steps to reproduce

  1. Upgrade vim (happens on artix and alpine)
  2. run vim

Expected behaviour

My color scheme to not completely get overwritten.

Version of Vim

9.1.1065-1 (artix), 9.1.1105-r0 (alpine)

Environment

Operating systems: alpine and artix
terminal: foot
$TERM=foot
shell: bash and ash
vim installed through the distros' repositories

https://github.com/user-attachments/assets/1dbfe7b2-ea10-4db2-8edb-7c6d6c97327a

Logs and stack traces


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649@github.com>

shield29384shield29384 created an issue (vim/vim#16649)

Steps to reproduce

  1. Upgrade vim (happens on artix and alpine)
  2. run vim

Expected behaviour

My color scheme to not completely get overwritten.

Version of Vim

9.1.1065-1 (artix), 9.1.1105-r0 (alpine)

Environment

Operating systems: alpine and artix
terminal: foot
$TERM=foot
shell: bash and ash
vim installed through the distros' repositories

https://github.com/user-attachments/assets/1dbfe7b2-ea10-4db2-8edb-7c6d6c97327a

Logs and stack traces


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649@github.com>

λmolinae

unread,
Feb 16, 2025, 12:01:16 AM2/16/25
to vim/vim, Subscribed

I fixed this by switching to neovim


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661246703@github.com>

amolinae06amolinae06 left a comment (vim/vim#16649)

I fixed this by switching to neovim


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661246703@github.com>

λmolinae

unread,
Feb 16, 2025, 12:06:03 AM2/16/25
to vim/vim, Subscribed

please share your configuration to assist you further


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661248202@github.com>

amolinae06amolinae06 left a comment (vim/vim#16649)

please share your configuration to assist you further


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661248202@github.com>

ud1w

unread,
Feb 16, 2025, 1:26:53 AM2/16/25
to vim/vim, Subscribed

same issue here

Artix
vim 9.1.1065-1
bash 5.2.037-1
XTerm 397
$SHELL = xterm-256color

normal colorscheme loads initially:

default.png (view on web)

but then changes after pressing any key or scrolling:

changed.png (view on web)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661275369@github.com>

ud1wud1w left a comment (vim/vim#16649)

same issue here

Artix
vim 9.1.1065-1
bash 5.2.037-1
XTerm 397
$SHELL = xterm-256color

normal colorscheme loads initially:

default.png (view on web)

but then changes after pressing any key or scrolling:

changed.png (view on web)


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661275369@github.com>

shield29384

unread,
Feb 16, 2025, 1:32:41 AM2/16/25
to vim/vim, Subscribed

Few things to note:
I downgraded vim and its working fine
As shown in the video even running --clean produces this issue, however I found that running vim as vim -u NONEXISTENTFILE fixes the colors from changing, but of course, you don't have a config...


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661277974@github.com>

shield29384shield29384 left a comment (vim/vim#16649)

Few things to note:
I downgraded vim and its working fine
As shown in the video even running --clean produces this issue, however I found that running vim as vim -u NONEXISTENTFILE fixes the colors from changing, but of course, you don't have a config...


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661277974@github.com>

Christian Brabandt

unread,
Feb 16, 2025, 3:27:59 AM2/16/25
to vim/vim, Subscribed

Upgrade vim (happens on artix and alpine)
run vim

What kind of reproduction steps is this please?

Vim enables termguicolors automatically, if it detects the terminal supports this. However, due to the async nature of querying the terminal, this is noticable and causes
I'll revert this behaviour for now.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661317695@github.com>

chrisbrachrisbra left a comment (vim/vim#16649)

Upgrade vim (happens on artix and alpine)
run vim

What kind of reproduction steps is this please?

Vim enables termguicolors automatically, if it detects the terminal supports this. However, due to the async nature of querying the terminal, this is noticable and causes
I'll revert this behaviour for now.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2661317695@github.com>

Christian Brabandt

unread,
Feb 16, 2025, 3:36:04 AM2/16/25
to vim/vim, Subscribed

Closed #16649 as completed via 27822a0.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/16649/issue_event/16323643969@github.com>

ynn

unread,
Feb 22, 2025, 3:35:46 AM2/22/25
to vim/vim, Subscribed

Having exactly the same issue after upgrading to 9.1.1100 (macOS).

9.1.1043 (Arch Linux) doesn't have this problem.

It seems guifg, guibg, etc. are suddenly started being respected instead of ctermfg, ctermbg, etc.
Manually setting set notermguicolors solved the problem.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2676092301@github.com>

your-diaryyour-diary left a comment (vim/vim#16649)

Having exactly the same issue after upgrading to 9.1.1100 (macOS).

9.1.1043 (Arch Linux) doesn't have this problem.

It seems guifg, guibg, etc. are suddenly started being respected instead of ctermfg, ctermbg, etc.
Manually setting set notermguicolors solved the problem.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2676092301@github.com>

Dave Eddy

unread,
Feb 25, 2025, 2:58:03 PM2/25/25
to vim/vim, Subscribed

Having exactly the same issue after upgrading to 9.1.1100 (macOS).

9.1.1043 (Arch Linux) doesn't have this problem.

It seems guifg, guibg, etc. are suddenly started being respected instead of ctermfg, ctermbg, etc. Manually setting set notermguicolors solved the problem.

same issue here - fixed it on macos with set notermguicolors as well, thank you!


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2683150200@github.com>

bahamas10bahamas10 left a comment (vim/vim#16649)

Having exactly the same issue after upgrading to 9.1.1100 (macOS).

9.1.1043 (Arch Linux) doesn't have this problem.

It seems guifg, guibg, etc. are suddenly started being respected instead of ctermfg, ctermbg, etc. Manually setting set notermguicolors solved the problem.

same issue here - fixed it on macos with set notermguicolors as well, thank you!


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/16649/2683150200@github.com>

Reply all
Reply to author
Forward
0 new messages