From b4df434aeacf35de93f825e64c84abce641c11f1 Mon Sep 17 00:00:00 2001
From: NotAShelf <NotAShelf@users.noreply.github.com>
Date: Sat, 20 Jul 2024 13:02:29 +0000
Subject: [PATCH] deploy: 8b15271f6364286e11aa6c1f9fda8e02c3ec581b

---
 release-notes.html | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/release-notes.html b/release-notes.html
index 3d2cf4c..e9288fc 100644
--- a/release-notes.html
+++ b/release-notes.html
@@ -186,7 +186,11 @@ currently open.</p></li><li class="listitem"><p>Remove vim-tidal and friends.</p
 blending issues in component separators.</p></li><li class="listitem"><p>Add [ts-ereror-translator.nvim] extension of the TS language module, under
 <code class="literal">vim.languages.ts.extensions.ts-error-translator</code> to aid with Typescript
 development.</p></li><li class="listitem"><p>Add [neo-tree.nvim] as an alternative file-tree plugin. It will be available
-under <code class="literal">vim.filetree.neo-tree</code>, similar to nvimtree.</p></li></ul></div>
+under <code class="literal">vim.filetree.neo-tree</code>, similar to nvimtree.</p></li><li class="listitem"><p>Add <code class="literal">print-nvf-config</code> &amp; <code class="literal">print-nvf-config-path</code> helper scripts to Neovim
+closure. Both of those scripts have been automatically added to your PATH upon
+using neovimConfig or <code class="literal">programs.nvf.enable</code>.</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: circle;"><li class="listitem"><p><code class="literal">print-nvf-config</code> will display your <code class="literal">init.lua</code>, in full.</p></li><li class="listitem"><p><code class="literal">print-nvf-config-path</code> will display the path to <span class="emphasis"><em>a clone</em></span> of your
+<code class="literal">init.lua</code>. This is not the path used by the Neovim wrapper, but an
+identical clone.</p></li></ul></div></li></ul></div>
 </div>
 
 </div>