all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Hyatt <ahyatt@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: contact@karthinks.com,  emacs-devel@gnu.org,  sskostyaev@gmail.com
Subject: Re: LLM Experiments, Part 1: Corrections
Date: Wed, 24 Jan 2024 11:00:42 -0400	[thread overview]
Message-ID: <m2sf2mhj39.fsf@gmail.com> (raw)
In-Reply-To: <p91mssvjrfb.fsf@google.com> (T. V. Raman's message of "Tue, 23 Jan 2024 20:17:44 -0800")

On Tue, Jan 23, 2024 at 08:17 PM "T.V Raman" <raman@google.com> wrote:

> All very good points, Kartik!
>
> Some related thoughts below:
>
> 1. I think we should for now treat  prose-rewriting vs code-rewriting as
>    separate flows -- but that said, limit our types of "flows"
>    to 2. More might emerge over time, but it's too early.

How do you see the code and prose rewriting requiring different UI or processing?

> 2. Multi-step flows with LLMs are still early -- or feel early to me; I
>    think that for now, we should just have human-in-the-loop at each
>    step, but then leverage the power of Emacs to help the user stay
>    efficient in the human-in-the-loop step, start with simple things
>    like putting point and mark in the right place, populate Emacs
>    completions with the right choices etc.

It can't be at every step, though. Maybe you wouldn't consider this a
step, but in my next demo, one step is to get JSON from the LLM, which
requires parsing out the JSON (which tends to be either the entire
response, or often in a markdown block, or if none of the above, we
retry a certain amount of times). But agreed that in general that we do
want humans to be in control, especially when things get complicated.



  reply	other threads:[~2024-01-24 15:00 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 [this message]
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
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=m2sf2mhj39.fsf@gmail.com \
    --to=ahyatt@gmail.com \
    --cc=contact@karthinks.com \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    --cc=sskostyaev@gmail.com \
    /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.