-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
type(getchar()) return 1 for < #12487
Labels
Comments
On 2020-06-13 14:45, Wang Shidong wrote:
* |nvim --version|: NVIM v0.5.0-345-g0b49cb67f
Could you try nightly?
* Terminal name/version: NO
* |$TERM|: NO
I think these might be important - I can't reproduce this on linux+kitty.
|
From Gitter:
|
wsdjeg
added a commit
to SpaceVim/SpaceVim
that referenced
this issue
Jun 13, 2020
I checked and |
Looks like this was fixed in equalsraf/neovim-qt#134 . Test with neovim-qt v0.2.16.1 (or later) https://github.com/equalsraf/neovim-qt/releases/tag/v0.2.16.1 |
justinmk
changed the title
type(getchar()) return 1 for <
Sep 8, 2020
type(getchar())
return 1 for <
adelin-b
pushed a commit
to adelin-b/SpaceVim
that referenced
this issue
Oct 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nvim --version
: NVIM v0.5.0-345-g0b49cb67fvim -u DEFAULTS
(version: ) behaves differently? yeah$TERM
: NOSteps to reproduce using
nvim -u NORC
Actual behaviour
it should print 0, but it is 1 in nvim
Expected behaviour
this should same as vim
The text was updated successfully, but these errors were encountered: