Peter Aronoff

This would be great to have as built-ins. I'd be up to try a PR if there is interest in adding these as well from the core team. (I'm currently...

@gpanders Good news: vim now has an `iput[!]` command that works like `put` but maintains indentation. It was just merged in vim: https://github.com/vim/vim/pull/16886. Once that gets picked up by neovim,...

@aktau Neovim should have `iput` shortly. https://github.com/neovim/neovim/pull/33076

> Interesting edge cases! Full disclosure: I am writing my own flag-parsing library (because clearly Go needs another one), and I came across these questions while h̶e̶a̶v̶i̶l̶y̶ b̶o̶r̶r̶o̶w̶i̶n̶g̶ consulting `ff`'s...

> I understand the perspective that `--debug=` should fail parsing. But I don't understand what that strictness achieves. Is there any situation where passing `--debug=` shouldn't be treated as if...

I wonder if this is a Nix problem rather than a Darwin or macOS problem. I've been using passage for several years on macOS (without Nix), and `passage -c` works...

Can I ask about the choice never to use the `start/` directory? More generally, I'm wondering why `vim.pack.add` always calls `:packadd` behind the scenes. Unless I'm confused, that makes it...

> > Can I ask about the choice never to use the start/ directory? > > Then if you want to disable plugins, you have to manually move them to...

> > Unless I'm confused, that makes it impossible to use `vim.pack` to install something that a user prefers to load only sometimes. > > Yes, it is possible. Call...

> The "will be removed after clean()" is intentional: "clean" means remove all plugins that are not used. But "are not used" is now ambiguous. Some plugins "are not used...