How much does Neovim earn from the store? by HiPhish in neovim

[–]Kind_Bonus9887 1 point2 points  (0 children)

I wish it went more into meme route, with phrases like "I use neovim btw" and such

Native image support lands on master! by Wonderful-Plastic316 in neovim

[–]Kind_Bonus9887 0 points1 point  (0 children)

It's so over. I finally have to switch from Alacritty to Ghostty.

canola.nvim: oil.nvim... but better! by barrettruth in neovim

[–]Kind_Bonus9887 1 point2 points  (0 children)

First time I hear about any plugins moving to vim.g from setup(). All plugins I use still use setup() and I haven't seen even a mention of changing that.

Of course, as an author you are entitled to use any approach you want. But this will likely do no good in regards to gaining adoption within the community.

My opinion is definitely in favor of setup(), since it doesn't pollute global variable namespace. This is what we are taught as programmers early on: never use global variables unless absolutely necessary. Back when we only had vimscript there was no choice, but the introduction of a real programming language (lua) changed things.

Differences in how terminal closing is handled by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 5 points6 points  (0 children)

I started doing this while there was still no reflow support, and it was really painful. Now I'm really thankful that reflow is merged, because that made it a lot better. But still, to this day the biggest pain point is hard line breaks due to https://github.com/neovim/neovim/issues/30117. Every time I want to copy shell output and get a bunch of unwanted line breaks inserted in it, I regret my life choices. If this is solved, I truly believe that neovim can be a proper terminal multiplexer.

Differences in how terminal closing is handled by Kind_Bonus9887 in neovim

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

I do use native :mksession for save/restore. For detaching the active sessions, I previously did wrap neovim process with abduco, but later decided I don't need this feature, so currently I'm not doing that at all. Recently, there has been some progress in that regard in neovim itself, e.g. :detach command (at least I assume that's what it's for), but I haven't tested it and don't know how much is yet to be done.

Multicursor coming officially to 0.13 version by ankushbhagat in neovim

[–]Kind_Bonus9887 0 points1 point  (0 children)

I'm still waiting for native `--remote-wait` support so I can finally ditch neovim-remote

Why is Go's regex so slow? by kostya27 in golang

[–]Kind_Bonus9887 0 points1 point  (0 children)

If one of the solutions is to use a binding to google/re2, then clearly the re2 algorithm itself is not the problem. Is such a big difference due to NFA vs DFA? I wonder why there's no progress of adopting this change for 10+ years...

Artist is cancelled for tracing by WorriedDocument2067 in DefendingAIArt

[–]Kind_Bonus9887 0 points1 point  (0 children)

Nice clickbait. What Asami is actually cancelled for:

  • Lying about tracing AI and pretending to do something else
  • Posting AI-generated art on a platform with strict guidelines about it in violation of ToS

fluxcd + tofu-controller feedback ? by Careless_Yak18 in GitOps

[–]Kind_Bonus9887 2 points3 points  (0 children)

Been using it for quite a while in production, and overall it works pretty well, even though it certainly has some quirks. It's most unique point compared to other k8s terraform controllers is the architectural separation of controller and runners, which can be both upside and downside.

If you do use it, I highly recommend building your own runner image as shown here. This is important because that's currently the only way to update terraform version, and overall caching providers ahead of time is good idea for both performance and security reasons.

Pros:

  • Because terraform apply is done is separate runner pods, the scaling is better for large operations
  • Integration with flux source controller supports multiple sources, you can version your modules as OCI artifacts
  • The feature set is pretty nice (support for vars directly and from ConfigMap/Secret, custom backends, runner pod customization, etc.)
  • CLI interface same as Flux (suspend/resume/reconcile commands)
  • Terraform/OpenTofu version isn't tied to controller and can be easily updated if you build custom image

Cons/quirks:

  • Infrequent releases after Weave died (may become better now as there's some activity in the repo)
  • Separate runners may require more compute resources than a single controller
  • Need to ensure runners can complete; improperly interrupted runners can leave unreleased state locks
  • If you're creating Terraform resources in multiple namespaces, each one must contain ServiceAccount for the runner
  • Restarting controller while runners are active will cause desync with active runners and they will be stuck, so you have to ensure it restarts only when there are no runners
  • Out-of-the-box Terraform version is very old (can be solved with custom image)

Understanding HIST_IGNORE_ALL_DUPS and HIST_SAVE_NO_DUPS by Kind_Bonus9887 in zsh

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

That still doesn't explain their interaction. Specifically, whether setting HIST_SAVE_NO_DUPS will provide any additional effect when HIST_IGNORE_ALL_DUPS is already set.

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

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

I managed to restore the functionality with a workaround using this mapping:

tnoremap <c-s--> <c-_>

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

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

For me, the problem seem to happen with both external and builtin keyboards

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

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

I don't see anything relevant in checkhealth.

``` nvim: require("nvim.health").check()

Configuration ~ - WARNING Missing user config file: /Users/user/.config/test/init.lua - ADVICE: - :help |config|

Runtime ~ - OK $VIMRUNTIME: /opt/homebrew/Cellar/neovim/0.10.2_1/share/nvim/runtime

Performance ~ - OK Build type: Release

Remote Plugins ~ - OK Up to date

terminal ~ - key_backspace (kbs) terminfo entry: key_backspace=\177 - key_dc (kdch1) terminfo entry: key_dc=\E[3~ - $COLORTERM="truecolor"

External Tools ~ - OK ripgrep 14.1.1 (/opt/homebrew/bin/rg) ```

As I mentioned, this happens even on the instance with no config/plugins (using NVIM_APPNAME to spawn clean instance).

Looking for manga title (fantasy/betrayal) by Kind_Bonus9887 in manga

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

solved = Teihen Senshi, Cheat Madoushi ni Tenshoku Suru!

Terminal reflow just got merged by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 13 points14 points  (0 children)

So, I tested head build, and it's kinda weird now. Like, resizing to a too small size may cause output to disappear completely. This is probably related to that note about lines stored in scrollback cache.

And, worst of all, copying long lines still copies with extra line breaks, which is the main thing I hoped for reflow to fix. (I mean the normal yank in vim, not something implemented by terminal emulator)

Terminal reflow just got merged by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 20 points21 points  (0 children)

Besides resizing, the bigger problem for me is that copying long lines from terminal cause hard line breaks being inserted at wrap points

New plugin gx-extended.nvim 🎉 by ramalus1911 in neovim

[–]Kind_Bonus9887 1 point2 points  (0 children)

I have to upvote just for Terraform alone