Skip to content
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

Works but brings up an error message every time I start vim #16

Open
revsuine opened this issue Jan 28, 2024 · 5 comments
Open

Works but brings up an error message every time I start vim #16

revsuine opened this issue Jan 28, 2024 · 5 comments

Comments

@revsuine
Copy link

Error detected while processing VimEnter Autoco
mmands for "*"..function background#clear_backg
round[17]..<SNR>30_clear_bg[12]..VimEnter Autoc
ommands for "*"..function background#clear_back
ground[17]..<SNR>30_clear_bg:
line    9:
E492: Not an editor command:  ctermfg=81 guifg=
#CDD6F4 ctermbg=NONE guibg=NONE
Press ENTER or type command to continue

Using Vim 9.1 on Arch Linux with Pathogen and Powerline, no other plugins.

Once I press enter it brings me to vim with the background transparent and it works fine, but I have to dismiss this error message every time I use vim. Do you know what's going on with this and how I can get rid of the error?

@revsuine
Copy link
Author

This appears to have been a conflict with Powerline. I just switched from Powerline to Airline and it works perfectly, no error message now. So the problem is resolved for me, but in case this is something you want to look into, I'll leave the issue open for now?

@revsuine
Copy link
Author

Never mind—the error message is back!

@tribela
Copy link
Owner

tribela commented Feb 2, 2024

Could you check the output when you type command :hi Normal ctermfg=81 guifg=#CDD6F4 ctermbg=NONE guibg=NONE?

@revsuine
Copy link
Author

revsuine commented Feb 2, 2024

So the error seems to happen inconsistently when I open vim. I'm not sure what triggers it. I just opened vim now without an error, and the command works fine. I will try next time I get the error and report back.

@revsuine
Copy link
Author

revsuine commented Feb 2, 2024

Ok, I noticed that it's more likely to happen if I open up a second vim session at the same time as an existing one, so I managed to trigger it by opening two vim sessions at once on two different files. I then ran that command and didn't get any output. The command seemed to work fine. I saw my terminal emulator (Alacritty) briefly flash, I assume to reset the background, and then just go back to being a transparent background (which it was before, like I said I'm still getting a transparent background I'm just also getting the error).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants