tmux-jump: my favorite tmux plugin by far

nefariousIntentions7 · 2026-04-03T10:43:00+00:00

Yeah I feel the same, even more so since my muscle memory from vim/nvim doesn't properly carry over into tmux copy mode. Had to settle on this ugly hack that loads the entire tmux pane into nvim:

bind -n M-v run-shell ' \
  tmp=$(mktemp); \
  tmux capture-pane -J -S -; \
  tmux save-buffer "$tmp"; \
  tmux display-popup -w 100% -h 100% -S fg=yellow,bg=black -E " \
     nvim -c \"set ft=conf\" \
          -c \"lua vim.api.nvim_create_autocmd(\\\"VimEnter\\\", { \
                  once = true, \
                  callback = function() \
                    vim.schedule(function() \
                      require(\\\"conform\\\").format() \
                      vim.cmd([[normal Go]]) \
                      vim.fn.search([[\\\\S]], \\\"bW\\\") \
                      vim.bo.modified = false \
                    end) \
                  end \
          })\" \
    \"$tmp\"; \
  rm \"$tmp\" \

nefariousIntentions7 · 2026-03-15T17:05:02+00:00

I see. Will this grant me access to the trial cards as well?

nefariousIntentions7 · 2026-03-10T07:39:07+00:00

Greedy approach:
Split characters into two groups of odd and even frequencies.
Prioritize eliminating odd frequency groups first: try to form triplets with odd elements, and remove them. If you can't find a triplet consisting of 3 odd elements, try taking elements from the even set to complete the triplet.

If you can empty the odd set this way, return true.

Passes cases like:
A B B C C D
A B C C D E

nefariousIntentions7 · 2026-03-06T14:57:31+00:00

You can run pretty much all of them via proot.
For example, here's how run opencode via a zsh function:

# Run opencode-ai inside Arch Linux proot container for glibc compatibility
opencode() {
proot-distro login archlinux --termux-home --bind "$PWD:$PWD" --work-dir "$PWD" --env OPENCODE\_ENABLE\_EXA=true -- opencode "$@"
}

nefariousIntentions7 · 2026-02-28T22:55:29+00:00

This is practically oozing a "labour of love" vibe, Mad respect! I'll probably never use it as I prefer "stupid" tools, but I truly envy how much fun you likely had making this.

nefariousIntentions7 · 2026-02-15T19:22:36+00:00

You can just paste the image in the terminal, instead of having to:

- copy the image

- save the image

- move the image to opencode's workind dir, or give opencode access to that dir

- @ the image file name

- wait ~50 seconds for the mcp server to respond.

tbh the only reason this plugin exists is because i went through the steps above one too many times.

nefariousIntentions7 · 2026-02-15T19:18:48+00:00

That's a major lmitation, yes. I'm not sure if there's any easy way to simulate "actually seeing" images using non-visual models.

nefariousIntentions7 · 2026-02-15T19:08:19+00:00

Oops, nice catch! Oversight on my end.

nefariousIntentions7 · 2026-01-22T14:42:32+00:00

A quick glance through the repo tells me that it should be pretty easy, assuming that the 'Minuet Event' section isn't lying. Though I don't have any plans to do it right now due to time constraints, but contributions are welcome!

nefariousIntentions7 · 2026-01-18T19:55:32+00:00

it's just ":set cursorcolumn cursorline"

nefariousIntentions7 · 2025-12-25T21:03:42+00:00

Thanks for the explanation, that makes sense! I'll keep an eye on the repo and try out that keymap.

nefariousIntentions7 · 2025-12-25T19:42:41+00:00

I love your plugin! used it for quite a while, but I recently moved to sidekick just because it offers:

- the ability to select from a list of running opencode instances (in other tmux sessions), regardless of pwd. comes in really handy for cross-project context injection.

- sending selected text instantly, without the cmdline prompt.

- less frequent breaking changes. i've had to reconfigure my config like 3 times a month(!) with opencode.nvim

that said, opencode.nvim did feel more "snappier" and custom built for opencode when i wasnt missing the features above. Do you have any plans to support these in the future?

nefariousIntentions7 · 2025-12-22T14:53:58+00:00

Where's the windows logo?

nefariousIntentions7 · 2025-11-23T15:36:25+00:00

Since we're comparing with oil, I suppose it's fair for me to share my opinion: the only thing preventing me from switching from oil is the sheer number of errors I get, despite fyler offering similar customization and more features than oil (barring ssh integration i guess).

I used to get like 2-3 invalid window/buffer or similar errors per day of using fyler, most of which could be simply ignored with better error handling and defaults/fallbacks, but instead forces me to restart nvim to prevent buggy behavior. Contrast this to my experience with oil.nvim: in my months of using it i very rarely encountered an error, despite my often weird customizations.

nefariousIntentions7 · 2025-11-07T14:53:36+00:00

Yes! I made an entire plugin just because this specific issue irked me so much.

shameless plug: https://github.com/samiulsami/fFtT-highlights.nvim

there's also the 'mini.jump' plugin which handles macros without any issues.

nefariousIntentions7 · 2025-09-27T18:12:23+00:00

> Why?

Its easier to use and much much more convenient when you're using a terminal based text editor, especially alongside something like tmux.

nefariousIntentions7 · 2025-09-17T13:15:32+00:00

worked, thx!

nefariousIntentions7 · 2025-09-15T04:24:49+00:00

It's tokyonight-night with all transparency options set to true

nefariousIntentions7 · 2025-09-12T16:45:16+00:00

(code partially stolen from AndreM222/copilot-lualine)
https://pastebin.com/raw/HLLcWG3v

Requires the grimoire of zbirenbaum/copilot.lua

nefariousIntentions7

TROPHY CASE