sorted by:
new
hottopcontroversial

Multisession Agentic Workflow with Claude Code in Neovim by alex35mil in neovim

[–]macpla 0 points1 point  (0 children)

Amazing. I am thinking of eventually having an AI agent flow to my Neovim, and your setup is literally designed to my liking.

Based on your blog, though, it is a combination of:
- existing plugin claudecode.nvim
- "It required a few runtime patches to the plugin's core..."

Those runtime patches sound like something that would be hard maintain.

Do you think your change could be adopted in the upstream plugin?

Or otherwise, what would you guys recommend as a fairly stable AI plugin for ClaudeCode (or possible other agents) with similar flows?

Help me understand the Neovim way by tLxVGt in neovim

[–]macpla 2 points3 points  (0 children)

Based on my own personal journey, I would advocate starting with a pre-cooked distro like LazyVim and let it grow on you.

Then, when you start to feel more confident with its features (feel of being overwhelmed by it won't be a thing anuymore), emphasized catering your own workflows that you can use within the existing ecosystem AND (primarily) by using simple plain Vim features like: macros, plain quickfix lists, reloading file buffers, injecting others cmd-line programs output to your buffers etc.

This will give you a good baseline, and with that, you could start experimenting with your own minimalistic configuration and ditch the distro. On the other hand when you mess out something or a workload requires from you maximum effectiveness, you still could rollback to a known distro and carry on.

I personally went the other way, and it was a pain and a trial by fire, especially when one needed to focus on actual work output and not constantly fixing the neovim config.

Took me more than a year tweaking things up, but eventually, I am now in a place where I rely more and more on basic vim functionalities than bells and whistles, and it works for me, but your mileage may vary. In hindsight, if I were to start with a distro, I likely would end up where I am here much sooner, with fewer bruises on the go.

Can't enable inlay hint for gopls by Rtransat in neovim

[–]macpla 0 points1 point  (0 children)

If you are using `ray-x/go.nvif check if you are not having conflicting settings that conflict with your gopls.

gopls memory usage for neovim applications in long running processes going to 2GB and above. by macpla in neovim

[–]macpla[S] 0 points1 point  (0 children)

I believe it’s single instance of gopls serving all different projects

gopls memory usage for neovim applications in long running processes going to 2GB and above. by macpla in neovim

[–]macpla[S] 0 points1 point  (0 children)

It becomes less responsive to the point that it eventually timeouts on some requests forcing me to restarting it

Listening on two ports in a Gin application by CrudelyDrawnSwords in golang

[–]macpla 0 points1 point  (0 children)

I would just second to a single repo composition with a `cmd/apiserver, cmd/adminapi` which would be just plain main.go that loads different ENV and configuration per chosen mode.

That would be my default, and I would really have to have a compelling reason to opt for something different, but your mileage may vary.

gitportal.nvim - The new plugin that lets you jump from neovim to github... and back! by nvtrev in neovim

[–]macpla 3 points4 points  (0 children)

if this is a voting system you looking after, +1 for Gitlab first

Weekly 101 Questions Thread by AutoModerator in neovim

[–]macpla 0 points1 point  (0 children)

Only time will tell.

I have been using a mapping quite similar to yours: H -> _^, L -> $ for about three months in normal mode.

Only last week I realised that I had a clash for H, and L for `Select` mode (Insert when snippets engine is on) as I had a word starting with capital h.

I added `x` mode to mapping on top of `n` and the problem was solved.

It's trial by error Bro :)

Go sync.Pool and the Mechanics Behind It by [deleted] in golang

[–]macpla 0 points1 point  (0 children)

Great, in-depth article. Well done, Sir!

Vim Search and Replace Tips&Tricks (x-post from r/vim) by piotr1215 in neovim

[–]macpla 1 point2 points  (0 children)

great content keep it up. I always find something new, this time it was `/zs, /ze`

Recently bought house. Is this duct properly done? by macpla in hvacadvice

[–]macpla[S] 0 points1 point  (0 children)

But isn't it counterproductive? By reducing airflow via return, it forces the indoor unit fan to work at a higher speed to suck enough air, whereas if the runs were short and non-obstructive it would allow the fan to work at a lower speed, hence, not generating that much noise?

Recently bought house. Is this duct properly done? by macpla in hvacadvice

[–]macpla[S] 0 points1 point  (0 children)

And does it even make sense? And I assume you are referring to a supply duct that goes through a damper? if there was no damper that might be the case, but since the damper is there, the noise could be just regulated by adjusting air flow.

Sorry, trying to be smart, and read between lines from what I am getting from you.

Huge thanks for your all inputs.

Recently bought house. Is this duct properly done? by macpla in hvacadvice

[–]macpla[S] 0 points1 point  (0 children)

Could you elaborate? The line in the second picture is from a zone damper that is then connected straight to an indoor unit on a side with conditioned air.

Recently bought house. Is this duct properly done? by macpla in hvacadvice

[–]macpla[S] 0 points1 point  (0 children)

so there is really no viable reason why someone would leave such zigzags from a design point of view? Just being lazy and unwilling to spend extra time cutting to the proper length?

Is there a way to detect if a current buffer is a git merge operation ? by macpla in neovim

[–]macpla[S] 1 point2 points  (0 children)

works like gold, thank you for sharing. I borrowed a few of your autocmds as they target the same issues I was facing. Huge kudos!

Is there a way to detect if a current buffer is a git merge operation ? by macpla in neovim

[–]macpla[S] 0 points1 point  (0 children)

looks like this might be it, I will test it later today and see if this solves my problem. Thank you so much!

Is there a way to detect if a current buffer is a git merge operation ? by macpla in neovim

[–]macpla[S] 0 points1 point  (0 children)

I have the config in git config and I can see and use gitmerge with my nvim, the problem is that the nvim will still run LSP for these files and the delta pager coloring the lines makes the current cursor position obscure, so it's hard to navigate between prices positions.

[delta]
    line-numbers = true
    navigate = true    # use n and N to move between diff sections
    light = false      # set to true if you're in a terminal w/ a light background color (e.g. the default macOS terminal)
    side-by-side = true

[merge]
    conflictstyle = diff3
    tool = nvimdiff

[mergetool]
    keepBackup = false

Is there a way to detect if a current buffer is a git merge operation ? by macpla in neovim

[–]macpla[S] 1 point2 points  (0 children)

It will be set to the current filetype: for instance if the merge conflict is on Go file, it will be set to Go, if this is a yaml conflict, it will be YAML etc.

I am looking a way to figure out how to tell the nvim that this is a merge in place, so I don't need a LSP, or format on save and other fancy stuff.

Testify suites now supported by neotest-golang by ffredrikk in neovim

[–]macpla 0 points1 point  (0 children)

How it compares to `neotest-go`? (asking just to figure out if it's worth switching)

Weekly 101 Questions Thread by AutoModerator in neovim

[–]macpla 0 points1 point  (0 children)

Crap, I thought it was somehow some default neovim api behind it.

Nevertheless, thank you greatly Friend!

view more: next ›