-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Settings getting cached somehow? #208
Comments
I think I just got very similar problem to yours and also trying to find out where the settings could be cached. I am updating the configuration and when I run nvim with galaxyline there is like 50 % change of getting the provider executed 🤔. For example given this peace of code in FileName provider: local long_fname = vim.fn.fnamemodify(vim.fn.expand("%"), ":~:.")
print(file_long_name_at_least_width + string.len(long_fname))
if wide_enough(file_long_name_at_least_width + string.len(long_fname)) then
fname = long_fname
else
fname = vim.fn.expand("%:t")
end sometimes it executes, prints the width and file is correctly expanded and sometimes there is just short version (which was previous configuration to show just short version e.g. filename). The filename is constant and screen is way wider than needed for the condition 🤔 |
ok, my problem was in naming actual components with the same name as in different parts of galaxyline ( I had local function check_component_exists(component_name)
for _,pos_value in pairs(M.section) do
for _,v in pairs(pos_value) do
if v[component_name] ~= nil then
return true,v[component_name]
end
end
end
return false,nil
end which iterates over all sections and try to find first match (although I am not exactly sure yet how did builtin function get there because apparently my |
I'm using a configuration I've taken from NvChad and edited a bit.
The main thing i've done is create a status item on the left side that represents the vim mode. There is already an item on the right side that does this, but I wanted to create a symbol based one.
Here is a shot of the left side of the bar when I open an empty buffer
My Issue
At one point when I was testing the above function, the function returned the
character instead of the question mark (a relic from the original function I copied). But now, even after I've long removed that line, I'm still seeing it when I should be seeing the correct indicators for Normal mode, etc.Here I've opened up an existing file in the same folder as before, and I'm still seeing the wind symbol?!?!?
What's more, I was able to change the
highlight
option for that block and the change was immediately reflected by turning the symbol red. Why is it not respecting the actual characters?The text was updated successfully, but these errors were encountered: