branch: externals/llm
commit 833bf528c913e2a68c80d4d59a20dab10e5508f2
Author: Andrew Hyatt <ahy...@gmail.com>
Commit: Andrew Hyatt <ahy...@gmail.com>
Add packages using llm to README
This will fix https://github.com/ahyatt/llm/issues/174.
---
README.org | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/README.org b/README.org
index 2455d53338..40b8e0b7d4 100644
--- a/README.org
+++ b/README.org
@@ -11,6 +11,12 @@ This library abstracts several kinds of features:
- Prompt construction: Create a prompt to give to an LLM from one more
sources of data.
Certain functionalities might not be available in some LLMs. Any such
unsupported functionality will raise a ~'not-implemented~ signal, or it may
fail in some other way. Clients are recommended to check =llm-capabilities=
when trying to do something beyond basic text chat.
+
+* Packages using ~llm~
+There a few packages using LLM (please inform us or open a PR to add anything
here):
+- [[https://github.com/s-kostyaev/ellama][ellama]], a package providing a host
of useful ways to use LLMs to chat and transform text.
+- [[https://github.com/douo/magit-gptcommit][magit-gptcommit]], a package
providing autogenerated commit messages for use with
[[https://magit.vc/][magit]].
+- [[https://github.com/ahyatt/ekg/][ekg]], a sqlite-backed notetaking
application that optionally interfaces with LLMs for note similarity and text
generation in response to notes.
* Setting up providers
Users of an application that uses this package should not need to install it
themselves. The llm package should be installed as a dependency when you
install the package that uses it. However, you do need to require the llm
module and set up the provider you will be using. Typically, applications will
have a variable you can set. For example, let's say there's a package called
"llm-refactoring", which has a variable ~llm-refactoring-provider~. You would
set it up like so:
