Autocomplete panics on Windows on version v0.1.0-dev.24 and later

[Enivex]

v0.1.0-dev.23 does work, so something was changed between these two builds

I do not know if logs are available anywhere, so I don't have any more information than this.

OS: Windows 11 23H2

[Cubxity]

Do you have the document in question?

[Enivex]

Do you have the document in question?

It'll happen with anything. Even something with just plain text in it.

[Cubxity]

I'm unable to reproduce this issue with the latest build (AppImage) on Fedora 38 Workstation. Please provide debug logs if you're able to. Set the RUST_LOG environment variable to debug.

[Enivex]

I'm unable to reproduce this issue with the latest build (AppImage) on Fedora 38 Workstation. Please provide debug logs if you're able to. Set the RUST_LOG environment variable to debug.

I would have to compile it myself in that case?

[Cubxity]

I'm unable to reproduce this issue with the latest build (AppImage) on Fedora 38 Workstation. Please provide debug logs if you're able to. Set the RUST_LOG environment variable to debug.

I would have to compile it myself in that case?

No. You should be able to run the compiled binary. I'm unsure how you would run the application with stdout on Windows, but I'm sure there's a way.

[Enivex]

I'm unsure how you would run the application with stdout on Windows, but I'm sure there's a way.

My googling leads me to believe there is no way without actually recompiling it

Edit: And I'm too dumb to figure out how to do that.

[Dherse]

@Enivex asked me to run it on Windows with RUST_LOG="debug" and attached are the logs from running with the following file: out.log

#set page("a4")

= Hello, world!

[Cubxity]

@Enivex asked me to run it on Windows with RUST_LOG="debug" and attached are the logs from running with the following file: out.log

#set page("a4")

= Hello, world!

Thank you. Seems like this may be a Windows-specific issue. Currently looking into it.

[Cubxity]

@Dherse could you try running the fix/windows-autocomplete branch?

[Dherse]

@Cubxity it appears to have fixed it ;) New log for reference: out.log