fvim VS nvim-scrollview

fvim and goneovim have support for gui-widgets.nvim which is a sort of protocol to define images and let Neovim GUIs display them.

fvim has a cool idea of having a common protocol for ui extensions: https://github.com/yatli/gui-widgets.nvim

While there is Avalonia.FuncUI you can use Avalonia with only F#/Xaml as well, take https://github.com/yatli/fvim as an example it's an avalonia app and doesn't use the FuncUI DSL but you'll have to handle your views in an OOP'ish way

I use fvim to meet the use case you describe. I love it.

For scroll bar, try nvim-scrollview

Nice. I was using dstein64/nvim-scrollview for scrollbar, but I am now tempted to switch to this one for search/gitsign integration.

Here are a few ideas to help: - Make sure your cursor stands out and is easy to find - Briefly explain windows, the status bar, and the tab bar, and make sure he knows that the file names are indicated at the BOTTOM of a window in the status bar - Make sure you have line numbers turned on and perhaps use this scrollbar plugin https://github.com/dstein64/nvim-scrollview so he knows where in a file you are - Explain what you are doing constantly, especially if the screen appears to be changing all of a sudden e.g., when you are scrolling up/down, jumping to the next search match, jumping through the jump list, jumping to a code symbol, navigating to a new file, opening up a file explorer, opening a fuzzy finder, opening a terminal, etc.

Virtual text. Diagnostics/linters are the obvious use case here, but there are other clever uses that plugin authors can use this for. (indent-blankline, nvim-scrollview, ...)

I use neoscroll for smooth scrolling and if you want a scrollbar then use this https://github.com/dstein64/nvim-scrollview

As of 79797a0, this workaround and a few others are now applied automatically. Workarounds that would clobber existing customizations are not applied.

I tried various ways to approximate WinScrolled, including usage of CursorMoved, but was unsatisfied with the options I tried. I documented some of the issues here. I recall also encountering an issue in Vim where the popup window for the scrollbar would occasionally become the active window, but I didn't spend much time debugging that, having switched to developing the plugin for Neovim.