From: Juri Linkov <juri@linkov.net>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: LLM Experiments, Part 1: Corrections
Date: Mon, 20 May 2024 20:28:31 +0300 [thread overview]
Message-ID: <86r0dwmlz4.fsf@mail.linkov.net> (raw)
In-Reply-To: <m2il3mj961.fsf@gmail.com> (Andrew Hyatt's message of "Mon, 22 Jan 2024 00:15:18 -0400")
> Question 3: How should we deal with context? The code that has the text
> corrector doesn't include surrounding context (the text before and after
> the text to rewrite), but it usually is helpful. How much context should we
> add? The llm package does know about model token limits, but more tokens
> add more cost in terms of actual money (per/token billing for services, or
> just the CPU energy costs for local models). Having it be customizable
> makes sense to some extent, but users are not expected to have a good sense
> of how much context to include. My guess is that we should just have
> a small amount of context that won't be a problem for most models. But
> there's other questions as well when you think about context generally: How
> would context work in different modes? What about when context may spread
> in multiple files? It's a problem that I don't have any good insight into
> yet.
I suppose you are already familiar with different methods
of obtaining the relevant context used by copilot:
https://github.blog/2023-05-17-how-github-copilot-is-getting-better-at-understanding-your-code/
https://thakkarparth007.github.io/copilot-explorer/posts/copilot-internals.html
etc. where tabs correspond to Emacs buffers, so in Emacs the context
could be collected from existing buffers like e.g. dabbrev-expand does.
next prev parent reply other threads:[~2024-05-20 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2il3mj961.fsf@gmail.com>
2024-01-22 18:50 ` LLM Experiments, Part 1: Corrections Sergey Kostyaev
2024-01-22 20:31 ` Andrew Hyatt
2024-01-22 22:06 ` T.V Raman
2024-01-23 0:52 ` Andrew Hyatt
2024-01-23 1:57 ` T.V Raman
2024-01-23 3:00 ` Emanuel Berg
2024-01-23 3:49 ` Andrew Hyatt
2024-01-23 1:36 ` João Távora
2024-01-23 4:17 ` T.V Raman
2024-01-23 19:19 ` Andrew Hyatt
2024-01-24 1:26 ` contact
2024-01-24 4:17 ` T.V Raman
2024-01-24 15:00 ` Andrew Hyatt
2024-01-24 15:14 ` T.V Raman
2024-01-24 14:55 ` Andrew Hyatt
2024-01-24 2:28 ` Karthik Chikmagalur
2024-05-20 17:28 ` Juri Linkov [this message]
2024-01-22 12:57 Psionic K
2024-01-22 20:21 ` Andrew Hyatt
2024-01-23 6:49 ` Psionic K
2024-01-23 15:19 ` T.V Raman
2024-01-23 19:36 ` Andrew Hyatt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0dwmlz4.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.