Open FulanXisen opened 1 year ago
What do uname
and uname -m
produce on your system?
Same for me:
$ uname
╭──────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────╮
│ kernel-name │ Darwin │
│ nodename │ xxx.local │
│ kernel-release │ 24.1.0 │
│ machine │ arm64 │
│ operating-system │ Darwin │
╰──────────────────┴───────────────────────────────────────────────────────────────────────────────────────────────╯
nvim version works as expected but I'm looking for the ghosting suggestions available in the vim version.
I just saw the virtual_text
option. I'll migrate to nvim since it's more suitable for my needs
My neovim is ➜ file ~/tools/nvim/bin/nvim tools/nvim/bin/nvim: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64] tools/nvim/bin/nvim (for architecture x86_64): Mach-O 64-bit executable x86_64 tools/nvim/bin/nvim (for architecture arm64): Mach-O 64-bit executable arm64
But I got ~/.codeium ➜ tree . └── bin └── 39080e89780bea461f7a46e6dc1026d80a3a353a └── language_server_windows_x64.exe
Why it happend? How to solve it?