The lack of tabs in #helixEditor caused me to open two instances on the same project. Unfortunately, it's written in #rustlang so the multiple rust-analyzer instances almost memory bombed my machine...

As the whole session started freezing, I wrongly blamed Firefox and started unloading tabs, but the fox was (mostly) innocent this time.

@bug Install more RAM!!! j/k, I know.
seriously: setup swap with zram or zswap to compress about half of your RAM and set swappiness to 95.

Another tip I once gave to a very memory constrained user is to use bacon instead rust-analyzer, but I guess you don't need that drastic actions.

@bug Have you tried the buffer line in #helixEditor ?

:set bufferline multiple

It shows open buffers basically like tabs. You can see them in action in this video at 2:41 https://www.youtube.com/watch?v=2P8GP1LEfKE

Helix Editor Tutorial 16 - Buffers

YouTube

@jeremie no, bufferline doesn't solve that problem.

Tab views (typically like vim) have a different set of buffers inside. You'd have different scopes for each tab. Each tab typically has several splits organized to work with that current context.

I enabled bufferline a while back, but I don't see its use. I'm likely going to drop it as it just clutters the view for no good reason.

Related: https://github.com/helix-editor/helix/pull/7109#issuecomment-4055358631

vim/neovim style tabs by nrabulinski · Pull Request #7109 · helix-editor/helix

closes #2295 This is a pretty highly requested feature which also is important to me which is why I took it upon myself to start the implementation of it. The implementation is very simple and basi...

GitHub
@bug have you tried https://codeberg.org/p2502/lspmux to make it only use one rust-analyzer?
lspmux

share one language server instance between multiple LSP clients to save resources

Codeberg.org
@laund someone pointed this to me, it indeed looks like it could be a workaround. But to be honest, I think I'm going to maintain a personal fork of helix with tabs support so I don't have to add workarounds on top of workarounds.
@bug ehh, it can be pretty useful even if you don't use it as a workaround for helix tabs, simply to persist the session a while after closing the editor. in that sense its perhaps a workaround for a oversight in the way LSP works, but its useful nonetheless