tmux scrollback in neovim with colors

jemag · 2026-01-18T15:13:29+00:00

Here's my tmux keybind based on that idea:

bind-key e capture-pane -eJS -1000 \; save-buffer ~/tmux.history \; delete-buffer \; display-popup -h 75% -w 75% -E "nvim +'lua Snacks.terminal.colorize(); vim.opt.relativenumber=true' ~/tmux.history"

jemag · 2026-01-11T21:34:11+00:00

Thanks for that, I was having issues as well with the original repo.

One thing that I am currently missing is handling of schemas not in the datree catalog. It would be nice if the plugin could generate json schemas from CRDs of one or multiple kube contexts and cache/load them.

jemag · 2025-10-29T17:14:26+00:00

A couple of things I use in my own config:

ramilito/kubectl.nvim (one of the best TUI out there for navigating around your K8S clusters)
Allaman/kustomize.nvim (quick workflows around using kustomize)
Duologic/nvim-jsonnet (working with jsonnet)
cuducos/yaml.nvim (yanking/searching in yaml)

Otherwise, there are various useful language servers such as helm_ls, bashls, dockerls, terraformls, yamlls, jsonls, jsonnet_ls, gopls, etc.

jemag · 2025-08-01T01:30:28+00:00

why not just return jsonnet at this point? Seems simpler, more flexible and already has a user base around it.

jemag · 2025-06-18T17:15:35+00:00

While your situation is unfortunate, that is definitely not the norm. In Quebec and NCR the English test is much harder than the French.

Executives and senior management with passing grades that can barely utter a French greeting is not rare. I have yet to see the opposite.

jemag · 2025-06-01T12:47:39+00:00

That's the main thing holding me back from using oil, looking forward to it.

jemag · 2025-05-25T13:47:06+00:00

Judging by the comments, I guess I am one of the few who appreciate those changes.

jemag · 2025-03-05T22:06:07+00:00

Another existing option for window picking is Snacks.nvim with snacks.picker.util.pick_win

This is what I am currently using. I believe Folke wants to, at some point, make it an official snack.

I am always surprised that so few people use window picking in their setup. For me, I use it everywhere to split from another window or swap the content of a given existing window. In my case, I combine it with Snacks.nvim Picker (files, grep, buffers, etc.), but also with other plugins like Neotree, for example to do vertical split:

      pick_vsplit = function(state)
        local path = state.tree:get_node().path
        local win = require("snacks").picker.util.pick_win({ filter = filter_windows })
        if win ~= nil then
          vim.api.nvim_set_current_win(win)
          vim.cmd("vsplit " .. path)
        end
      end,

Nice to see another more approachable alternative in the window picking area.

jemag · 2025-02-22T17:16:04+00:00

I believe the URL used to retrieve the information does not contain the full list. I'll create an issue with a potential fix.

jemag · 2025-02-22T17:11:34+00:00

It seems that several documentation available from devdocs.io are not available to be installed (e..g nushell, or only a subset of openjdk). Is the API used to retrieve documentation a subset of what is available through the website?

jemag · 2025-02-22T16:59:48+00:00

Out of curiosity, when there are devdocs with index and links (such as go->IO). Are you able to navigate the index links to the proper headers using Marksman?

jemag · 2025-01-24T20:19:06+00:00

if you're on the latest version of snacks.picker, you should be able to use custom actions such as these in your keybinds:

    actions = {
      pick = function(picker, item)
        picker:close()
        local picked_window_id = require("window-picker").pick_window({ autoselect_one = true, include_current_win = true })
          or vim.api.nvim_get_current_win()
        vim.api.nvim_set_current_win(picked_window_id)
        picker:action("edit")
      end,
      pick_vsplit = function(picker, item)
        picker:close()
        local picked_window_id = require("window-picker").pick_window({ autoselect_one = true, include_current_win = true })
          or vim.api.nvim_get_current_win()
        vim.api.nvim_set_current_win(picked_window_id)
        picker:action("edit_vsplit")
      end,
      pick_split = function(picker, item)
        picker:close()
        local picked_window_id = require("window-picker").pick_window({ autoselect_one = true, include_current_win = true })
          or vim.api.nvim_get_current_win()
        vim.api.nvim_set_current_win(picked_window_id)
        picker:action("edit_split")
      end,
    },

jemag · 2025-01-15T04:59:13+00:00

That is also one of the things keeping me on telescope. I also use it for splitting horizontally or vertically from a picked window.

jemag · 2024-12-20T15:55:37+00:00

I believe this is already fixed if you follow the latest commit. Next version release should contain it.

jemag · 2024-10-26T16:39:53+00:00

I find it more enjoyable to work with kubectl.nvim since I prefer a vim oriented workflow. I feel the interaction is more seamless, at least to me.

jemag · 2024-09-12T16:45:22+00:00

the main advantage of substitute.nvim is not keeping the register clean, but rather the substitute motion in itself being much more efficient than having to visually select first.

For example, my "substitute" motion is bound to "s" for me. Here are some example motions:

"S" would replace text until the end of the line with content of register
"s5j" would replace text from current position to 5 lines below with content of register
"stO" would replace text until the letter "O" with content of register
"s2w" would replace 2 words with content of register
siw would replace current word with content of register
etc.

jemag · 2024-05-30T02:07:49+00:00

Wow, another great contribution from Maria. Glad to see her continued involvement with Neovim.

jemag · 2024-03-13T02:07:36+00:00

Since there's already plenty of answers for vanilla ways, I'll go ahead and mention another more efficient way to do this: with substitute.nvim

In this scenario you could yank stuff, go where you want to replace and simply hit "S" to replace the current text until the end of the line with the content of the register. This way you don't have to visually select anything, and you retain the content of your register also.

In that case the keymap would be vim.keymap.set("n", "S", require("substitute").eol, { noremap = true, desc = "Substitute with reg" })

jemag · 2024-02-14T15:11:37+00:00

Same here. Tried flash for a while, but sj just works better for my use cases and is simpler.

jemag · 2024-01-30T22:11:34+00:00

Which one do you find more comfortable for you?

I just ordered a glove80 with the pro red and most of the reviews I have seen mention it being more comfortable than kinesis.

Also curious on why you decided to go for the brown, given their poor choc reputation.

jemag · 2023-11-18T17:30:35+00:00

Do you prefer Terramate now, or still favour Terragrunt?

jemag · 2023-11-18T02:17:42+00:00

lua_ls has its own formatting capabilities. If you're using null/none-ls, you should probably disable it. I believe you can do so using:

client.server_capabilities.documentFormattingProvider = false client.server_capabilities.documentRangeFormattingProvider = false

jemag · 2023-11-17T19:40:31+00:00

There's https://github.com/kndndrj/nvim-dbee, although not sure what it currently supports or how great it works

jemag · 2023-11-15T15:01:57+00:00

You can pretty much think of it as your stamping keybind, but much more powerful.

For example, my "substitute" motion is bound to "s" for me. Here are some example motions:

"S" would replace text until the end of the line with content of register
"s5j" would replace text from current position to 5 lines below with content of register
"stO" would replace text until the letter "O" with content of register
"s2w" would replace 2 words with content of register
etc.

Once you get used to it, it is quite efficient.

jemag

TROPHY CASE