lualine.nvim icon indicating copy to clipboard operation
lualine.nvim copied to clipboard

Bug: Intro screen cleared immediately

Open fitrh opened this issue 2 years ago • 19 comments

Self Checks

  • [x] I'm using the latest lualine.
  • [x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem

  • Run neovim with --clean option and load lualine
    nvim --clean \
        -c 'packadd lualine.nvim' \
        -c 'lua require("lualine").setup()'
    

Expected behaviour

Neovim opens with an intro screen

Actual behaviour

The intro screen cleared immediately

Minimal config to reproduce the issue

No need for minimal config as the reproduction steps mimic a fresh install of neovim and skip all initialization step

fitrh avatar Aug 01 '22 06:08 fitrh

https://github.com/nvim-lualine/lualine.nvim/issues/259#issuecomment-1200083574

Intro gets cleared on first redraw and setting stl in scheduled function seems to act as a redraw.

shadmansaleh avatar Aug 01 '22 06:08 shadmansaleh

I've asked the nvim devs . It's a bug in neovim.

shadmansaleh avatar Aug 04 '22 03:08 shadmansaleh

Any updates?

jacobsonryan avatar Sep 12 '22 23:09 jacobsonryan

Any updates?

No it's a low priority issue for neovim. Most likely I'll have to fix it myself but I don't currently have time for this. You can try out the dashboard like plugins to give you a nicer intro if you find this annoying the default one doesn't really provide much info. Since this can't be fixed in lualines side I think this will take a while to get resolved.

shadmansaleh avatar Sep 17 '22 14:09 shadmansaleh

This was fixed on my latest build (7fc5f66)

fitrh avatar Sep 22 '22 11:09 fitrh

Still having the same problem, with the latest lualine and neovim v0.9.0-dev-3-gafb7efb373.

yannjor avatar Oct 02 '22 13:10 yannjor

@yannjor can you reproduce it using the minimal config?

fitrh avatar Oct 02 '22 13:10 fitrh

Yes, I removed everything from my config leaving only require("lualine").setup() and still the same.

yannjor avatar Oct 02 '22 13:10 yannjor

I can confirm it, it's weird, my full config does not have the issue but the minimal config has

fitrh avatar Oct 02 '22 14:10 fitrh

Same here

tony-sol avatar Oct 14 '22 13:10 tony-sol

Disabling separators keeps the intro screen up for me. @fitrh @Tony-Sol any chance this explains the difference between your full config and the minimal config?

ryanburda avatar Nov 09 '22 14:11 ryanburda

@ryanburda you are right, I didn't realize it since I always disable the separator, the following setup doesn't have this issue

nvim --clean \
    -c 'packadd lualine.nvim' \
    -c 'lua require("lualine").setup({ options = { section_separators = "", component_separators = "" } })'

fitrh avatar Nov 09 '22 15:11 fitrh

Solution with empty separators is not working for me - it skips intro screen even with empty require('lualine').setup {}

Full config here: https://github.com/Tony-Sol/.config/blob/master/nvim/lua/configs.lua

UPD 29.07.2023

After switch from packer to lazy.nvim, solution with empty string as section separators works for me. Still keep looking how to save desired separators and start screen

tony-sol avatar Feb 03 '23 13:02 tony-sol

In my case startup screen is displayed by only set options.section_separators = ''

sahibalejandro avatar Feb 07 '23 04:02 sahibalejandro

I noticed it works if you call require('lualine').setup from after/plugin.

wardw avatar Mar 02 '23 20:03 wardw

options.section_separators = '' also works for me. But of course I don't want that. I like having separators.

jsatk avatar May 23 '23 19:05 jsatk

I was not sure what was causing this issue. I came here looking for something else but found this issue. Its happening to me and I was trying to fix it but nothing mentioned above worked for me.

lalitmeeq avatar Jun 12 '23 13:06 lalitmeeq

Also experiencing this issue.

CFiggers avatar Jan 04 '24 14:01 CFiggers

Same here. However, Neovide 0.12.2 (on Windows 10) doesn't show this behavior, independent of the no-multigrid setting. image

To my understanding, Neovide is just a "client"; is it possible that the issue could be patched outside of nvim upstream after all?

jives avatar Feb 21 '24 06:02 jives