nvim-lualine / lualine.nvim

A blazing fast and easy to configure neovim statusline plugin written in pure lua.
MIT License
6.19k stars 466 forks source link

Bug: lualine is not showing in neovim nightly #220

Closed luisvgs closed 3 years ago

luisvgs commented 3 years ago

Self Checks

How to reproduce the problem

Install lualine.nvim using vim-plug. Use the minimal configuration provided by the documentation:

require('lualine').setup{}

Actual behaviour

The statusline is not showing after installation.

Expected behaviour

Statusline shows as expected.

Aditional information

I noticed that when running :checkhealth lualine suddenly appears during the checkhealth process, and dissapears a few seconds after. I tried disabling my colorscheme and other plugins that might be interfering with the plugin's behavior, but got not luck at all. I'm attaching my dotfiles at the bottom of this issue just in case. My current neovim version: NVIM v0.5.0-dev+1233-g82ac44d01

Minimal config to reproduce the issue

I'm using the vimrc configuration provided by the documentation.

let g:lualine = {
    \'options' : {
    \  'theme' : 'gruvbox',
    \  'section_separators' : ['', ''],
    \  'component_separators' : ['', ''],
    \  'disabled_filetypes' : [],
    \  'icons_enabled' : v:true,
    \},
    \'sections' : {
    \  'lualine_a' : [ ['mode', {'upper': v:true,},], ],
    \  'lualine_b' : [ ['branch', {'icon': '',}, ], ],
    \  'lualine_c' : [ ['filename', {'file_status': v:true,},], ],
    \  'lualine_x' : [ 'encoding', 'fileformat', 'filetype' ],
    \  'lualine_y' : [ 'progress' ],
    \  'lualine_z' : [ 'location'  ],
    \},
    \'inactive_sections' : {
    \  'lualine_a' : [  ],
    \  'lualine_b' : [  ],
    \  'lualine_c' : [ 'filename' ],
    \  'lualine_x' : [ 'location' ],
    \  'lualine_y' : [  ],
    \  'lualine_z' : [  ],
    \},
    \'extensions' : [ 'fzf' ],
    \}
lua require("lualine").setup()
Config [https://github.com/bluretrece/dotfiles/blob/main/nvim/keybindings.vim](url)
luisvgs commented 3 years ago

Solved the issue. I noticed I still had galaxyline enabled :-)