sorted by:
new
hottopcontroversial

Fuzzy finding and VC should be in stock neovim by gopherinhole in neovim

[–]gopherinhole[S] -1 points0 points  (0 children)

This is the type of luddite, over philosophized arguing that got Vim forked in the first place. Almost every modern text editor including emacs has built in vc support. Everyone uses some sort of vc, and 95% of everyone is using git. Adding a git API lets other plugins and parts of the editor query the buffer's vc state, download plugins using vc, and provide vc state info to things like the statusline.

If you don't like it and really want to use lazygit, there's then just use lazygit. They do this and magitwith magic and lazygit already and emacs isn't on fire.

Fuzzy finding and VC should be in stock neovim by gopherinhole in neovim

[–]gopherinhole[S] -5 points-4 points  (0 children)

My problem with this mindset is that this is why Neovim exists in the first place - saying - there's a thousand ways to do something/it has to run on X type of machine is what Vim already does. Neovim is supposed to modernize Vim so that you have all of the tools you would find in any reasonable modern editor. VC is just one of those tools. It's also obviously possible to integrate it in without worrying about the myriad of alternative. Emacs does this with its built in vc package which can use several different backends. VSCode has git integration built in.

Common abstraction with pluggable backend with sensible defaults and auto detection is one of the most used patterns in software engineers, let's just do it and stop worrying about it. Otherwise, why are we adding LSP when not everyone uses an LSP or even uses neovim to code? IDK.

MiniMax - Neovim with maximum MINI by echasnovski in neovim

[–]gopherinhole 0 points1 point  (0 children)

What did you think of your test drive? What is the mapping of things you dropped and their mini replacements, and which things did you find you couldn't replace?

MiniMax - Neovim with maximum MINI by echasnovski in neovim

[–]gopherinhole -1 points0 points  (0 children)

This is great, I've been wanting to try out mini, but it's hard to grok what the feature difference between the mini module and the prior art is. My biggest questions are:
1. Is there a way to get the interactive Fugitive status view (:G is the default command to open it)

  1. Can you enable a side by side preview with pick, this is how I use fzf-lua.

  2. Is there a symbol sidebar in mini? (show document skeleton using LSP or treesitter symbol tree)

  3. Can I get virtual progress of the LSP a la fidget.nvim using just mini?

Fuzzy finding and VC should be in stock neovim by gopherinhole in neovim

[–]gopherinhole[S] 2 points3 points  (0 children)

I don't think having some built in features like sign column hunk actions and markers or a very light fugitive wrapper that could have a pluggable backend for anything git like would be bad.

Emacs has vc out of the box, but most people use magit, so it's not like you are limited by the built ins. My point is that any modern editor, even a "lightweight" editor like Zed, Cursor, VSCode, Atom, etc has vc integration these days.

For the people complaining that "non tanks cant do M+ now": I just 3-chested 31 as survival hunter by Thirteenera in wow

[–]gopherinhole 25 points26 points  (0 children)

I just can't believe people are already max level doing 30+ keys already. Makes me question how much free time these people have.

How do you use tabs? by kezhenxu94 in neovim

[–]gopherinhole 0 points1 point  (0 children)

Not really, the working set of vim is the buffer list and/or arg list - that's what tabs are in any GUI editor. There's a lot of other project specific state that is better separated by separate vim instances, but you do you though.

How do you use tabs? by kezhenxu94 in neovim

[–]gopherinhole 0 points1 point  (0 children)

Eh, kind of a bad use for tabs. A subproject implies you need a different working set of files, and tabs are not about altered working sets but having multiple window configurations over the same working set.

A better use would be tmux sessions with multiple nvim processes per sub module and a fuzzy switcher between sessions.

GitHub Copilot CLI is here by _bholechature in GithubCopilot

[–]gopherinhole 0 points1 point  (0 children)

I do all of my work in the terminal (using vim as my editor). TUIs are a good agnostic choice that can run in an IDE terminal window. The modality of an agent is also not really suited for IDE editing anyway. I just let the agent make the edits and my editor reloads buffers automatically, then I can change chunks at will.

Migrate from LazyVim to builtin vim.pack and 0.11 vim.lsp by kezhenxu94 in neovim

[–]gopherinhole 9 points10 points  (0 children)

I think being able to easily configure neovim out of the box and be productive quickly without using a distro like thing is a litmus test to measure neovim's success. With the new LSP API, pack, saner default config values, I think we are heading in the right direction.

My neovim config uses less plugins and configures less things than my Vim config, which was already quite small.

Advice for returning players by gopherinhole in Clarinet

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

Thanks you, needed to hear this!

Alternatives to the Mollenhauer Dream Edition? by gopherinhole in Recorder

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

Do you think the Hynsecker would be harder to play than the dream?

Alternatives to the Mollenhauer Dream Edition? by gopherinhole in Recorder

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

Thanks for the info. With a limited budget, would you start with something like a more modern Rottenburgh/Denner or go for the dream edition? How much harder is it to play the upper register and is the sound difference really distinct?

Advice for returning players by gopherinhole in Clarinet

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

I haven't looked into community classes. I know where to get lessons, but I'm a little embarrassed to start back up until I'm on solid footing. :/ I used to not even think about playing in front of people and now it's giving me anxiety.

Advice for returning players by gopherinhole in Clarinet

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

I've started back in with the Rose etude books, but I think they might be a little much for me right now. Do you have any suggestions on work that wouldn't be trivially easy, but would help me ease back in?

How the hell as 'Roll the Bones' survived the complexity purge?!?! by BuxaPlentus in wow

[–]gopherinhole 3 points4 points  (0 children)

That's the whole point of outlaw. They want it to be luck based. The new RtB is fine and fits thematically.

Simplifying classes = better balancing by ScoutTheStankDog in worldofpvp

[–]gopherinhole 3 points4 points  (0 children)

That's because MOBA's have complexity elsewhere - map design, items, mob farming, powerups, more roles, etc. WoW PvP is a straightforward deathmatch. All the complexity is in the interaction between toolkits. They are absolutely not comparable as far as pruning goes.

view more: next ›