My system information

Linux 5.13.12-arch1-1 x86_64 GNU/Linux

Issue I met

I am a Chinese user. And I used fcitx as the Chinese input method. However, I can't trigger the input panel like other neovim GUI or the TUI when I am using the nvui.

• Normal behavior in terminal

• In nvui

  It just outputs English nor creates the fcitx input panel.

My fcitx version:

fcitx version: 4.2.9.7

Opening Chadtree causes this error for me

terminate called after throwing an instance of 'msgpack::v1::insufficient_bytes'
  what():  insufficient bytes
[1]    3544750 abort (core dumped)  

Is it possible to manage multiple nvim instances, each instance contains an individual session. This can help me jump between each project without closing or opening a new nvui window.

I've tried mksession and some session managers. They can jump between session but I can't open a brand new workspace. I have to open file, clean up buffer and save session before I swich between those sessions. That's putting the cart before the horse.

I've seen goneovim did it: https://github.com/akiyosi/goneovim#workspaces. Don't know if it is possible to add this feature in nvui because I really love it.

Thanks for your contribution.

Hi, nvui should show an opening message because my vimrc contains an error. The message is invisible. To understand: this screenshot shows navi and nvim-qt side by side. https://pasteboard.co/LO3Wrz4TgOUT.png Thanks!

Just off the bat, this is what nvui looks like when I open it.

For starters, it's confused by my taskbar placement and hides the title bar behind it; this is remedied by using the Windows+Arrow keys of course.

Secondly, the correct font is not used; it renders a non-monospaced font. I have a ginit.vim, but nvui hasn't read any of it. How do I get it to read my configuration? I know that the problem stems from not having a monospace font (#32), but I've set a monospace font in configuration.

Speaking of setting, for some reason I can't see the status line no matter what. This means I can't see commands; they are below the window.

https://user-images.githubusercontent.com/59306451/131559040-37f2f269-a1ae-4f9f-81fa-ef496258d0b0.mp4

(Sorry about the recording; I just used the Powerpoint screen recorder. I captured the entirety of the nvui screen for sure.)

Now, I can set guifont to some fallback like Consolas after I get into the gui. And I'm sure I could set the window to open to whatever position I want it (just need to figure out where to configure it, or use the terminal). However, I still wouldn't be able to see the command line. Do you have any idea why this occurs? It occurs even with init.vim and ginit.vim empty.

I am on Windows 10, with neovim 0.5.0.

I just tried the newest release on Windows 10. Here are some issues, I can't experiment further after that:

• Font is broken
• The status bar is lost
• Is there any way I can speed up the animation? Otherwise, it's nice, looking for improvement

snapping the app to maximize or clicking the maximize button leaves a white border on the other screen (dual monitor) when using a frameless title bar, no issues if it's disabled. white border doesn't appear if it's snapped on half the screen or quarter, only happens in maximize. also doesn't appear on nvuitogglefullscreen. hopefully could be fixed soon, this is the only customizable title bar nvim gui i could find, and i've been loving it, thank you so much for your hard work.

• Fix crash on getting completion list (#36)
• Map Cmd key to C- key on Mac
• Add support for Super (D-) key
• Fix rendering issues on Mac (#70)
• Link ext_cmdline to default colors by default
• Fix alignment of popup menu info on ext_multigrid (workaround Neovim bug, can't be worked around without multigrid)
• Notify user of font families that couldn't be found

Make warnings errors in CMakeLists.txt, and then fix all the resulting errors.

I was not able to fix the errors about unknown macros, but I'm not sure where they are coming from or what to do to fix it. Looks like it's related to cppcheck but you're not using cppcheck...

When opening a terminal (using :term) and running an output-heavy application, after a while nvui crashes. The terminal where i started it from then says:

terminate called after throwing an instance of 'msgpack::v1::insufficient_bytes'
  what():  insufficient bytes

abort (core dumped)

Hello,

I'm trying out nvui and its been nice.

One issue I am having is I place diagnostic glyphs in the gutter. They seem to have some trouble rendering:

vim.api.nvim_command('sign define DiagnosticSignError text=🄴  texthl=Error linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignWarn text=🅆  texthl=Warning linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignInfo text=🄸  texthl=Warning linehl= numhl=')
vim.api.nvim_command('sign define DiagnosticSignHint text=🄷  texthl=Warning linehl= numhl=')

The above are the configuration lines. I believe these are just UTF characters as they are rendering right here on GitHub. Any idea?

When I open nvui the alpha dashboard page at startup is not centered and I cannot immediately use my shortcut keys, it first requires any key stroke which first centres the dashboard and shows properly and then another keypress to invoke any keybinding.

This is how it looks when it is first opened

After pressing any random key it recentres like this

And after that I am able to use any of the Neovim keybindings. This behaviour is not observed in either terminal neovim or any other GUIs. Also even after dashboard getting refreshed it still is not centred properly like in other instances.

This is how the dashboard page is actually supposed to look at startup

System Info

• OS: Arch Linux
• DE: Gnome 42.3(Wayland)
• Neovim Version: 0.7.2
• Nvui Version: 0.2.1(Installed nvui-git from AUR)

Hello devs,

I have just tried this amazing frontend for neovim and I must say, I am impressed with the quality.

That being said, the only downside is that it is extremely laggy on a 4k display. I cand easily reproduce this by shrinking down the nvui window and it works as expected and is fast, so I know for syre the resolution is the problem.

I have encountered this problem when trying neovide as well (see: https://github.com/neovide/neovide/issues/1299) and initially thought it was a problem related to their implementation, but now I am not so sure, because it might be something deeper than the UI. The only frontend that has fast performance for me on a 4k display up until now is nvim-qt.

Could we maybe somehow coordinate between these three (your project, neovide and nvim-qt) to try and find a solution to this?

Description

nvui reads <C-^> as <^> which is invalid in vim & neovim.

Environment

• Arch Linux
• nvui latest git version (as of the time of creation of this issue)

There are already some issues mentioning not working keys, so I don't want to bother too much when there is no time. Maybe it'll be good to create an issue that groups them and create an overview which helps when there is more room for it.

#134 #143

Another one that looks like it has problems is <. E.g., when mapping it to preserve selection while outdenting, no selection is preserved in nvui. vim.keymap.set("v", "<", "<gv", { desc = "Outdent" })