branch: elpa/gptel
commit b34a1356ec25e2e4887413fba0a282ba35fdd7a2
Author: Karthik Chikmagalur <[email protected]>
Commit: Karthik Chikmagalur <[email protected]>
NEWS: Mention limited Vterm support for gptel-send
* NEWS (New features and UI changes): Mention limited support for
gptel-send in Vterm buffers. Improve explanation of saving
preset references to chat buffers.
---
NEWS | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 6b956473818..be63fc09a89 100644
--- a/NEWS
+++ b/NEWS
@@ -47,7 +47,21 @@
- If a preset has been applied in a gptel chat buffer, saving the
buffer to a file causes the preset to be recorded along with the
- other metadata (model, backend, tools etc).
+ other metadata (model, backend, tools etc). This makes it possible
+ to associate any collection of gptel settings/preferences with the
+ chat file, and not just the few properties that gptel writes to the
+ file otherwise. But resuming this chat with the preset settings
+ applied requires that the preset be defined, so the chat file will
+ be less self-contained.
+
+- =gptel-send= now works in Vterm buffers in a limited way. Responses
+ will be inserted into Vterm buffers, but without streaming. The
+ respond-in-place option to overwrite queries with responses in Vterm
+ buffers is supported as well, but might be buggy if your shell
+ prompt is "rich" and has many dynamic elements.
+
+ Support for =gptel-send= in Term/Ansi-Term and Eat buffers is not
+ yet available but planned.
** Notable bug fixes
