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

inconsistent visibility in buffers #64

Closed
Adictya opened this issue Jan 7, 2021 · 3 comments
Closed

inconsistent visibility in buffers #64

Adictya opened this issue Jan 7, 2021 · 3 comments

Comments

@Adictya
Copy link

Adictya commented Jan 7, 2021

I really like the plugin however I am facing an issue where the galaxy line is not visible upon initial execution of neovim. If I call a buffer refresh via something like whichkey window in the example , it becomes visible. However on opening a neo-tree split-buffer it disappears again only to come after I close that split-buffer

Demonstration.
galaxyvimissue

Issue Reproduction-
This is my config
The issue seems to be theme agnostic however I am using this theme
I have done no additional customizations besides loading the theme on my part

@glepnir
Copy link
Member

glepnir commented Jan 8, 2021

config gl.short_line_list is a table value is some special buffer filetypes. when you in this buffer will show short_line. so you need config short_line . Also when you trigger WinLeave ,it also load short_line

-- if in LuaTree or vista or dbui buffer will load short_line
gl.short_line_list = {'LuaTree','vista','dbui'}

gls.short_line_left[1] = {
  BufferType = {
    provider = 'FileTypeName',
    separator = '',
    separator_highlight = {colors.purple,colors.bg},
    highlight = {colors.fg,colors.purple}
  }
}


gls.short_line_right[1] = {
  BufferIcon = {
    provider= 'BufferIcon',
    separator = '',
    separator_highlight = {colors.purple,colors.bg},
    highlight = {colors.fg,colors.purple}
  }
}

check your config short_line just return a empty .so you don't see anything.

@Adictya
Copy link
Author

Adictya commented Jan 8, 2021

Apologies for not reading the documentation , thank you for your fixes that seems to have fixed most of my issue.

@glepnir
Copy link
Member

glepnir commented Jan 9, 2021

Aha It's okay. now I will close this issue.

@glepnir glepnir closed this as completed Jan 9, 2021
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