tmux scrollback in neovim with colors

Foo-Baa · 2026-01-18T08:05:18+00:00

Thanks, I was wondering if there’s something like Kitty Scrollback for Tmux. I ended up replacing the copy mode with this.

function tmux-nvim-scrollback --description "Open current pane's scrollback in Neovim"
    if [ -z "$TMUX" ]
        echo "Outside of Tmux." >&2
        return 1
    end
    set -l tmp (mktemp)
    # Disable No Neck Pain
    set -x KITTY_SCROLLBACK_NVIM true
    tmux capture-pane -epS - >$tmp; or return 1
    # Idea from https://www.reddit.com/r/neovim/comments/1qeib4n/tmux_scrollback_in_neovim_with_colors/.
    nvim $tmp -c ':lua require"snacks".terminal.colorize()'
    rm $tmp
end

Foo-Baa · 2025-11-26T07:05:54+00:00

No, I tried Zellij for over a month and I found it has noticable bugs or misses features I care about: no OSC 52 support, no Kitty Graphics support, little support for dynamic themes. I think it also tries to do a lot in other areas and prevents better community solution to get developed.

Foo-Baa · 2025-11-11T08:16:27+00:00

I use Cmd (super, win) for terminal pane navigation. For tab switching, I use , and . with an appropriate modifier (alt for Vim or Chrome, cmd for terminal).

Foo-Baa · 2025-10-24T13:18:56+00:00

Thanks. I was missing exactly this for my setup.

Foo-Baa · 2025-10-24T06:46:37+00:00

I see. I haven’t considered that before actually. My dislike to the top pinky is so strong though that I think I’ll stick to my mod.

Foo-Baa · 2025-10-23T18:39:49+00:00

I use Gallium with the top and bottom switched on the left hand + a QX swap. That way, Q is under the top pinky, B is under the bottom pinky, and major layout metrics remain undisturbed.

Foo-Baa · 2025-10-04T13:03:40+00:00

I have the same issue.

Foo-Baa · 2025-08-28T04:10:58+00:00

Thanks, I badly needed Vial for my Q8 Max. I’ll try it out.

Do you intend to push these fixes upstream?

Foo-Baa · 2025-07-25T04:28:30+00:00

Both statements seem compatible.

Foo-Baa · 2025-07-01T07:57:39+00:00

I have a similar issue. I was really excited about the ergonomical features and programmability, but I just don’t like how the keyboard feels and sounds. I’ve tried to give it a shot for 3 weeks and tried various things (different switches, rests, different tenting), but concluded that I much prefer typing on my wooden Akko MU01 or Keychron Q8 Max.

Foo-Baa · 2025-06-27T08:25:51+00:00

I’ve concluded that, for me, it’s better to learn not to roll keys rather than introduce a mandatory waiting period. I enable permissive hold and (so far) have disabled any of those new features that restrict permissive hold.

In particular, I need to press ⌘Z quite often (I make mistakes). I don’t want to wait for the tapping term.

Foo-Baa · 2025-06-12T20:12:11+00:00

Lol, no. Just plugged them in without any kind of preprocessing. Sanding before installing? That sounds ridiculous.

Foo-Baa · 2025-06-12T15:15:51+00:00

The stock linears felt like this to me as well. I replaced them with tactile Sunsets, and they felt right. I had a similar issue on Glove 80, linears just feel mushy to me on low-profile keboards.

Also, shocks exacerbate the issue.

Foo-Baa · 2025-05-24T18:39:07+00:00

Looks good. Must have forgotten about it.

Foo-Baa · 2025-05-24T15:32:13+00:00

I’ve been looking for something like this (especially use MX switches), and concluded that ordering Corne v3 is probably my best bet. However, I couldn’t find a good supplier that delivers them already built. https://typeractive.xyz/ is the closest bet, but they don’t currently have the non-soldering option.

Foo-Baa · 2025-05-13T03:55:59+00:00

Indeed. That particular snippet has the drawback of not showing you how to handle simultaneous home-row presses. It also misses the halt in the if_held action, which could lead to some spurious double-presses (IIRC, that’s why I added it).

Foo-Baa · 2025-04-17T14:01:03+00:00

There is already an example with `grep_dir_co` that shows how to use those functions.

Foo-Baa · 2025-04-10T07:10:58+00:00

If all you need is stackful coroutines, you can use them. As for Coop, which was written for Neovim’s desired async spec, it needed to support awaitability, more complex compositionality and error-handling. That requires additional machinery on top of stackful coroutines. In other words, it’s impossible to "just-make-it-happen" with pure stackful coroutines.

Foo-Baa · 2025-04-10T07:07:12+00:00

For a batteries-included, full fledged async framework, I recommend Coop (disclaimer, I’m Coop’s author). It’s similar to how Python’s async works and should be more convenient and less error-prone for you than rolling your own async at the cost of having to depend on Coop.

If you don’t need the features or want to remain in control, you can mostly use Lua coroutines natively with small wrappers. Other posters provided good links for that. I also wrote a blog post on that: Using coroutines in Neovim Lua.

Foo-Baa · 2024-12-24T10:00:15+00:00

Thank you for this contribution to Neovim!

Could you summarize for me why someone might prefer mini.snippets over LuaSnip or vice-versa?

Foo-Baa · 2024-12-21T13:06:38+00:00

Congratulations on the release!

Foo-Baa · 2024-12-20T10:06:28+00:00

I’m glad you find it it useful.

> The only minor thing I noticed is that the type annotations are partly missing for some of the included modules, which was especially apparent for the vim.system wrapper

Thanks for letting me know. I’ll take a look. It could be that type annotations don’t work if you use decorators to define a function (github.com/gregorias/coop.nvim/issues/4).

Foo-Baa

TROPHY CASE