Helix (editor)

now that we use zellij we can do the same with

C-l = ":sh zellij run -f -x 10% -y 10% --width 80% --height 80% -- lazygit"  

I also am interested in

Great idea – I modified slightly:

C-l = ":sh zellij run -f -x 5% -y 5% --width 90% --height 90% -- bash -c \"lazygit && zellij action close-
pane\""

maybe use sh instead of bash

1 Like

Helix 25.01 release

https://helix-editor.com/news/release-25-01-highlights/https://helix-editor.com/news/release-25-01-highlights/

A few features that stand out:

Inline diagnostics

Add the following to ~/.config/helix/config.toml

[editor.inline-diagnostics]
# Minimum severity to show a diagnostic on the primary cursor's line.
# Note that `cursor-line` diagnostics are hidden in insert mode.
cursor-line = "error"
# Minimum severity to show a diagnostic on other lines:
other-lines = "error"

And you get nice inline diags like:

Picker columns

Some pickers now have columns, such as the symbol picker as shown below:

You can filter on the kind column by: %kind method

1 Like

:lsp-restart

One thing I’ve been using a bit lately in helix is:

:lsp-restart

In Zephyr, when I change my build target, everything changes in the build, so it is useful to do a full restart on the clang LSP.

In Elm, after I install a new Elm package, seems we need to restart the LSP for things to work properly.

Being able to restart the language server without restarting the editor is super useful – kind of like :config-reload.

The first every crash I’ve observed in Helix after ~1year of very heavy use.

helix
thread 'main' panicked at helix-core/src/transaction.rs:499:9:
Positions [(6595, AfterSticky), (6596, BeforeSticky)] are out of range for changeset len 4628!
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

It also interesting to me how different programming environments respond to problems. The worst is a crash with some cryptic message like “seg fault”. Seems Rust is doing some better and has the provision to display a backtrace.

I have seen crash when I try to start helix in a non-existent directory, e.g. in a shell you might be in a directory which has been deleted from another shell. Trying to start helix crashes