Providers are the thing I spend most of my time on while admittedly very
few users use it (I can only think of deoplete now) and it's going to disappear anyway.
We have no tests for it because of the previous reasons.
Before this patch:
nix path-info -Sh .#neovim
/nix/store/smd007xlbsx35y42rri5xlqhjgajz9in-neovim-0.11.6 365.0 MiB
After:
nix path-info -Sh .#neovim
/nix/store/4cr60j05l3pirhhrcs5hqb9rzj854n5r-neovim-0.11.6 240.6 MiB
To restore old behavior, pass `{withPython3= true; withRuby = true; }`
to the neovim wrapper.
as an attempt to simplify configuration:
instead of having wrapping arguments + an optional neovim configuration
let's always generate a neovim configuration.
The change should be transparent for most users, and require
intervention for users that fulfill both conditions:
- using remote plugins (rare already)
- that set `wrapRc = false` in wrapNeovimUnstable without loading later
the generated luaRcContent
The fix is then to pass as wrapping arguments the wrapper's generated config via
(wrapNeovimUnstable neovim-unwrapped { } ).overrideAttrs(oa: { wrapperArgs = oa.wrapperArgs ++ [ ''--cmd "lua dofile('${writeText "init.lua" oa.luaRcContent}')"'' ]; })
neovim: avoid creating empty newlines
Use the correct attribute names after the cacheVersion -> fetcherVersion
rename and mention fetchNpmDeps's fetcherVersion parameter as well.
Addresses review feedback from #470517.
Different editions of Balatro have essentially the same Lua codebase,
delegating to a native bridge `love.platform` to handle cloud
functionality like profiles and achievements. These bridges are not
part of the standard LÖVE SDK, and hence aren't provided
by`pkgs.love`.
`withBridgePatch` uses the local filesystem for loading/saving games,
and short-circuits the other bridge functions. This enables the Google
Play and Xbox PC editions of the game to be played with the open source
LÖVE runtime.
