Yatao Li
Revisiting this: neovim thinks FVim is holding all the states in each tab while FVim is only holding one grid. To solve this, each tab should have its own grid...
Thanks for reporting. I'll tackle with OSX bugs when I get access to a Mac.
- `git clone https://github.com/yatli/fvim` - `cd fvim` - `dotnet run` Make sure you have `dotnet` and `nvim` in your `$PATH` Also, we're running .NET Core 3.1 now: https://dotnet.microsoft.com/download/dotnet-core/3.1
@VVVFO I believe the dvorak problem is exactly like the "de" case for German layout. However, we cannot simply capture the textual input and stick modifiers onto it because some...
I'm not familiar with iTerm keyboard input logic but I believe it will be simply ignored. In a terminal, `` maps to a non-printing ASCII key, see: https://www.physics.udel.edu/~watson/scen103/ascii.html , so...
Oh and, the ultimate solution is to run a little virtual machine in parallel and when there's a modified key, feed it non-modified version of the "virtual key code" and...
- `guifont`? - `guifontwide`? - screenshot? please, be specific. :)
It probably means that the fonts indeed have different heights or ascents. I've seen similar behavior on Iosevka Slab vs. nerdfont symbols. Not sure how to fix this though.
hey @ayehome maybe I can implement different heights for gf vs. gfw?
> My opinion is to give priority to solving the Z-index problem Should've been fixed in 0.3.520?