Andrej Kolčin

Yeah, it must be something else in the configuration, because I have an identical keybinding, and it works correctly in Vi mode (Linux, also 0.99.0)

```sh running 300 tests test arg_parser::test::version_flag ... ok test arg_parser::test::plugins_with_file_paths_no_dash_at_first ... ok test arg_parser::test::plugins_with_file_paths_no_dash_after_first ... ok test arg_parser::test::incremental_arg ... ok test commands::config::test::config_add ... FAILED test commands::config::test::should_output_resolved_config ... FAILED test commands::editor::test::should_output_editor_plugin_info...

Updated the comment. The commit is 35c795a7

``` ~/fork/dprint> cargo test commands::config::test::config_add -- --nocapture ... Finished `test` profile [unoptimized + debuginfo] target(s) in 0.18s Running unittests src/main.rs (target/debug/deps/dprint-ada9ff8ad2d279ac) running 1 test thread 'commands::config::test::config_add' panicked at crates/dprint/src/test_helpers.rs:43:58: Could...

And I'm also running this on Alpine, which uses musl as its libc, not glibc. And `/tmp` is a tmpfs, but it doesn't seem like the tests get to the...

Huh. This makes all tests pass, but the test command still fails: ```sh ~/fork/dprint> cargo test ... warning: `dprint` (bin "dprint" test) generated 2 warnings Finished `test` profile [unoptimized +...

And it's also not deterministic. Sometimes 20 tests are completed before this error, sometimes 40 or 60. But all of the finished tests succeed

I got some help, and we managed to locate the segfault: ```gdb #0 __restore_sigs (set=set@entry=0x7ffff3f28f70) at ./arch/x86_64/syscall_arch.h:40 #1 0x00007ffff7fa9845 in raise (sig=sig@entry=6) at src/signal/raise.c:11 #2 0x00007ffff7f78c21 in abort () at...

@dsherret I checked with wasmer 4.3.2, but the issue persists. I think I'll stop the port for now and come back in a few months, after the dependencies move forward

Thanks for the help nonetheless!