Since then, I've improved it a bit. I introduced the YOLO mode --dangerously-skip-permissions as default when I open CC, and I need to split the window pane on my desktop monitor to 1/3 and on my laptop monitor to ½.

The split introduced a new function, which is called on keypress.

local function split_for_claude()
	local screen = wezterm.gui and wezterm.gui.screens().active.name or ""
	local percent = 50

	if screen == EXTERNAL_MONITOR then
		percent = 33
	end

	return act.SplitPane({
		direction = "Right",
		command = { args = { "bash", "-lc", "claude --dangerously-skip-permissions" } },
		size = { Percent = percent },
	})
end

EXTERNAL_MONITOR is the name of the external monitor. The name you will get from opening the Debug Overlay and calling wezterm.gui.screens().

And the key settings are:

config.keys = {
  -- ...
	{
		key = "Enter",
		mods = "LEADER",
		action = wezterm.action_callback(function(window, pane)
			window:perform_action(split_for_claude(), pane)
		end),
	},
  -- ...
}

Now I hit leader+enter and CC opens in a 1/3 or ½ split depending on the display. :)

57 of #100DaysToOffload
#log #wezterm #code #dev
Thoughts? Discuss...

Overall, I was ok with what GH Copilot delivered. But I heard a lot about the new kids in town and wanted to explore them. I was split between Codium and Supermaven and decided for Supermaven after their announcement that they will join Cursor.

GitHub Copilot

For 2 years now, I have been using Copilot. 99% of the time just for code completion. Very rarely, I've written a comment to tell it what it needs to do. In the past months, I was not satisfied anymore with the results it gave me. I was editing the results more than it saved me writing them.

The start with Copilot was also a bit bumpy. I needed to get a flow. Sadly, the original Vim/Neovim extension by TPope was slow and cumbersome to use. Luckily, there was a Copilot Plugin written in Lua which was fast enough to get a good flow. For auto-completion, I usually use CMP, but I don't want to mix Copilot with CMP and took another approach. This was by getting the suggestions and accepting theme with meta+tab and cycling through suggestions with meta+[ and meta+]. That was enough for me, to have a nice auto-completion for more than 1,5 years. 😎

With the rise of the new kids on the block, the suggestions got worse with every day. So, a replacement was needed. :) I waited until my subscription ended and then tried the new one.

Supermaven

I can't say much besides, all works flawlessly. From account creation to plugin installation, everything worked on first-try.

They maintain a GitHub repo, from where you get your instructions on how to set up Supermaven in Neovim.

Here is my config:

return {
	"supermaven-inc/supermaven-nvim",
	config = function()
		require("supermaven-nvim").setup({
			keymaps = {
				accept_suggestion = "<m-tab>",
				clear_suggestion = "<m-k>",
				accept_word = "<m-j>",
			},
			ignore_filetypes = { cpp = true }, -- or { "cpp", }
			disable_inline_completion = false, -- disables inline completion for use with cmp
		})
	end,
}

There is no cycling between suggestions, but it's no problem, so far, there was no need for them. 😅

It's insane how instant the suggestions came and, until now, on point. A feature which is now a must-have for me is, that you can accept words of the suggestion, if you don't want it all.

On my supermaven.com account is a Chat credit. This is something I haven't figured out how to use. Maybe it is only available in these bloated IDEs. 🤷

I'm more than happy with it and enjoy everyday coding with it, so far.

59 of #100DaysToOffload

#log #code #neovim #supermaven

Thoughts? Discuss...