You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<INFO> [22:04:20] Vi-normal mode enabled.
CORRUPTION WARNING in SBCL pid 121384 tid 121424:
Memory fault at 0x37d (pc=0x7fe18030ca70, fp=0x7fe1603fd780, sp=0x7fe1603fd630) tid 121424
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
<WARN> [22:04:25] Warning: Error on GI-GTK thread: Unhandled memory fault at #x37D.
The text was updated successfully, but these errors were encountered:
Vonfry
changed the title
Crash when delete the last buffer if setting vi-normal keybindings in document-mode.
Crash when deleting the last buffer if setting vi-normal keybindings in document-mode.
Apr 15, 2024
I can reproduce and it's an interesting bug. nkeymaps/conditions:override-existing-binding is responsible for the crash, but I don't quite understand why it doesn't silently warn in this case (as it does in other).
Given that this bug can only be reproduced when connected via Slynk/Swank, it is rather low priority.
Can I help with a workaround in the meantime? What are you trying to achieve?
Given that this bug can only be reproduced when connected via Slynk/Swank, it is rather low priority.
It can also be reproduced when setting it in user init files, why I found this.
Although I said "crash", the process hanged instead of termination because debugger is invoked (*debug-on-error* is nil). Instead, I kills the process manually.
Can I help with a workaround in the meantime? What are you trying to achieve?
Thanks. I can avoid this myself without deleting the last alive buffer.
The original goal is to create a new buffer with default-new-buffer-url like the action on other keyscheme without this issue.
Describe the bug
Precise recipe to reproduce the issue
nyxt -S --no-init
start-slynk
vi-normal-mode
delete-current-buffer
The crash also appears with
cua
ordefault
keyscheme sometimes, but I cannot reproduce it.Information
show-system-information
:Output when started from a shell
Backtrace
The text was updated successfully, but these errors were encountered: