Luka Markušić

As much as I love `lazygit`, for this specific thing maybe you would be better off with [vim-fugitive](https://github.com/tpope/vim-fugitive/) or maybe [vim-gitgutter](https://github.com/airblade/vim-gitgutter?tab=readme-ov-file#hunks) for staging the current hunk. Just my two cents,...

> vim-fugitive is nice, but it's staging tool is a pure wrapper around git stage -p, which does not support line-by-line staging. `vim-fugitive` does support partial staging, you just have...

This looks pretty close to `lazygit` to me:   In any case, this is a discussion better suited for the [`lazygit` discord channel](https://discord.gg/ehwFt2t4wt) since it is pretty off topic.

I have an even simpler example that results in a `segfault`: ```python import simpleaudio as sa wave_obj = sa.WaveObject.from_wave_file('/any/sound/file.wav') playing = wave_obj.play() print('Started playing!') playing.wait_done() print('Done playing!') ``` I can...

Same, nothing that's missing in current master that would justify a delay. ✅

Does e.g. `docker images` work with that environment variable outside of `lazydocker`?

It does seem hackish, [here's](https://github.com/mark2185/lazygit/commit/8efce01b5f5df8692ece3a2c41c004dcfcb848cc) an alternative which isn't configurable, but it doesn't use floating points. Make of it what you will :)

> Is that linked commit in master @mark2185 ? Nope, it was a draft _for a_ draft PR that never actually got created.

Please build https://github.com/wagoodman/dive/pull/473 from source to fix it.

@RafaelWO `dive` probably didn't affect that, check your docker context and switch it if needed: ```bash $> docker context ls ```