branch: elpa/gptel
commit 8ccdc31b12a1f5b050c6b70393014710f8dbc5c8
Author: Karthik Chikmagalur <karthikchikmaga...@gmail.com>
Commit: Karthik Chikmagalur <karthikchikmaga...@gmail.com>
README: Mention llm and Ellama
* gptel.el (header): Add email
* README.org (Alternatives): Mention llm and Ellama
---
README.org | 2 ++
gptel.el | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/README.org b/README.org
index de902c2825..9aa0a9a1ae 100644
--- a/README.org
+++ b/README.org
@@ -796,6 +796,8 @@ Features being considered or in the pipeline:
Other Emacs clients for LLMs include
+- [[https://github.com/ahyatt/llm][llm]]: llm provides a uniform API across
language model providers for building LLM clients in Emacs, and is intended as
a library for use by package authors. For similar scripting purposes, gptel
provides the command =gptel-request=, which see.
+- [[https://github.com/s-kostyaev/ellama][Ellama]]: A full-fledged LLM client
built on llm, that supports many LLM providers (Ollama, Open AI, Vertex,
GPT4All and more). Its usage differs from gptel in that it provides separate
commands for dozens of common tasks, like general chat, summarizing code/text,
refactoring code, improving grammar, translation and so on.
- [[https://github.com/xenodium/chatgpt-shell][chatgpt-shell]]: comint-shell
based interaction with ChatGPT. Also supports DALL-E, executable code blocks
in the responses, and more.
- [[https://github.com/rksm/org-ai][org-ai]]: Interaction through special
=#+begin_ai ... #+end_ai= Org-mode blocks. Also supports DALL-E, querying
ChatGPT with the contents of project files, and more.
diff --git a/gptel.el b/gptel.el
index 17a22e384a..4a4c15764f 100644
--- a/gptel.el
+++ b/gptel.el
@@ -2,7 +2,7 @@
;; Copyright (C) 2023 Karthik Chikmagalur
-;; Author: Karthik Chikmagalur
+;; Author: Karthik Chikmagalur <karthik.chikmaga...@gmail.com>
;; Version: 0.8.6
;; Package-Requires: ((emacs "27.1") (transient "0.4.0") (compat "29.1.4.1"))
;; Keywords: convenience
@@ -1106,6 +1106,7 @@ the response is inserted into the current buffer after
point."
(encode-coding-string
(gptel--json-encode (plist-get info :data))
'utf-8)))
+ ;; why do these checks not occur inside of `gptel--log'?
(when gptel-log-level ;logging
(when (eq gptel-log-level 'debug)
(gptel--log (gptel--json-encode
