Skip to content
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

opening red and pressing 'q' causes crash (and sometimes produces strange output) #51

Open
erf opened this issue Feb 28, 2024 · 4 comments

Comments

@erf
Copy link

erf commented Feb 28, 2024

recreate:

cargo run
q

crashes with the following message:

index out of bounds: the len is 2212 but the index is 2212

I also noticed sometimes when i open red again after that, it crashes automatically. I think it is because some process (the LSP client?) is not closed down properly and is producing some escape codes still. I noticed this when i opened my own videditor in insert mode.

version: d1b337c
os: macOS

@fcoury
Copy link
Contributor

fcoury commented Feb 28, 2024

Can you send me your red/config.toml please? I can't replicate this one.

@fcoury
Copy link
Contributor

fcoury commented Feb 28, 2024

I was able to replicate it in insert mode I think!

@fcoury
Copy link
Contributor

fcoury commented Feb 28, 2024

Here's the backtrace:

panicked at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/string.rs:1643:9:
assertion failed: self.is_char_boundary(idx)
panicked at src/lsp/mod.rs:296:22:
called `Result::unwrap()` on an `Err` value: SendError { .. }

@erf
Copy link
Author

erf commented Feb 28, 2024

Can you send me your red/config.toml please? I can't replicate this one.

I copied the default_config.toml file at the mentioned commit.

You didn't get the error when pressing "q" in normal mode?

That's a different error than mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants