-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
nvim 100% CPU And Frozen When modified.enabled = true
#1878
Labels
bug
Something isn't working
Comments
Workaround: modified = {
enable = false, |
Nothing in logs after opening tree. |
very odd:
|
@chomosuke I'd be most grateful if you could look into this one. |
alex-courtis
pushed a commit
that referenced
this issue
Jan 3, 2023
alex-courtis
added a commit
that referenced
this issue
Jan 9, 2023
alex-courtis
added a commit
that referenced
this issue
Jan 9, 2023
…uire_confirm (#1887) * fix(#1878): nvim frozen on no name buffer when modified.enable (#1879) * feat(api): add api.config.mappings.active, api.config.mappings.default (#1876) * feat(api): add config.mappings.current and config.mappings.default * feat(api): add config.mappings.current and config.mappings.default * feat(api): add config.mappings.current and config.mappings.default * Implement turning off y/n prompt for file deletion * Refactor different prompt configs to single ui table * Remove unused fields * add ui.confirm doc, format/tidy * trash.require_confirm -> ui.confirm.trash * Fix nil value trash field Co-authored-by: Richard Li <[email protected]> Co-authored-by: Telman Babayev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
nvim will freeze and process will use 100% CPU when first editing a no name new buffer.
Neovim version
Operating system and version
Linux 6.1.1-arch1-1
nvim-tree version
since dcc344c
Minimal config
Steps to reproduce
nvim -nu /tmp/nvt-min.lua
Expected behavior
No response
Actual behavior
No response
The text was updated successfully, but these errors were encountered: