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

bug: blank window after quitting the dashboard or typing window #21

Open
akashkennedy opened this issue Jan 25, 2025 · 7 comments
Open
Labels
help wanted Extra attention is needed

Comments

@akashkennedy
Copy link

OS: Arch Linux
WM: Swayfx
Terminal: kitty

I'm using latest version of neovim. When I try to exit from the typing UI it shows only a blank window without any content in it. Also I can't quit typr or neovim.

@siduck
Copy link
Member

siduck commented Jan 25, 2025

ig this is just with lazyzvim :/

@siduck
Copy link
Member

siduck commented Jan 25, 2025

simplescreenrecorder-2025-01-25_12.33.18.mp4

or this happens when dashboard is enabled. can you try with a new file?

@allanabiud
Copy link

I don't know if this is related but after closing the Dashboard, an overlay remains that dims my screen.

Image

@siduck siduck added the help wanted Extra attention is needed label Jan 29, 2025
@davidsteinberger
Copy link
Contributor

davidsteinberger commented Jan 29, 2025

@siduck Hitting <ESC> feeds q which seems to cause that. Could this be changed to use nvim_win_close()?
For everyone facing this issue close it out with this command: :lua vim.api.nvim_win_close(0, false)

Note: Try it out with nvim -u repro.lua (repro.lua)

@siduck
Copy link
Member

siduck commented Jan 30, 2025

@davidsteinberger i dont see why hitting esc feeds q? where do you get that from

@davidsteinberger
Copy link
Contributor

Sry, spoke too soon. Volt hast 2 close methods and I looked at the wrong one. The point still holds though:
Both keys are mapped by volt and call utils.close(val) but that might leave the window intact.

For testing purpose I simply checked the win in the after_close callback and closed it there:

volt.mappings {
  bufs = { state.buf, dim_buf },
  winclosed_event = true,
  after_close = function()
    if api.nvim_win_is_valid(state.win) then
      api.nvim_win_close(state.win, false)
    end
    state.reset_vars()
  end,
}

@siduck
Copy link
Member

siduck commented Jan 30, 2025

volt just has 2 mappings, both dont conflict etc. the question's that why does it happen only when dashboard is in the background?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants