This commit is contained in:
Ching Pei Yang 2026-05-07 08:32:29 +10:00 committed by GitHub
commit 8db9454b1d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 5 additions and 4 deletions

View file

@ -7,10 +7,10 @@
viewBox="0 0 1024.0 1024.0"
version="1.1"
id="SVGRoot"
sodipodi:docname="neovim-flake-logo-work.svg"
sodipodi:docname="nvf-logo-work.svg"
xml:space="preserve"
inkscape:version="1.2.2 (b0a8486541, 2022-12-01)"
inkscape:export-filename="neovim-flake-logo-work.png"
inkscape:export-filename="nvf-logo-work.png"
inkscape:export-xdpi="192"
inkscape:export-ydpi="192"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"

Before

Width:  |  Height:  |  Size: 44 KiB

After

Width:  |  Height:  |  Size: 44 KiB

View file

@ -84,6 +84,9 @@ jobs:
runs-on: ubuntu-latest
if: "!contains(github.event.pull_request.title, '[skip ci]')"
strategy:
# avoid having 2 jobs building ndg when no cache is available
# TODO: there is probably a better way
max-parallel: 1
matrix:
package:
- docs

View file

@ -243,8 +243,6 @@ better prepare for breaking changes.
**A**: Quite possibly. **nvf** started as "neovim-flake", which does mean it is
and will remain flakes-first but we might consider non-flakes compatibility.
Though keep in mind that **nvf** under non-flake environments would lose
customizability of plugin inputs, which is one of our primary features.
**Q**: I prefer working with Lua, can I use nvf as a plugin manager while I use
an imperative path (e.g., `~/.config/nvim`) for my Neovim configuration instead