From: Bruno Barbier <brubar.cs@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Including AI into Emacs
Date: Mon, 09 Dec 2024 23:56:41 +0100 [thread overview]
Message-ID: <675775ac.050a0220.1b7ef7.6fe2@mx.google.com> (raw)
In-Reply-To: <Z1dbvDS0VfZ8c12j@lco2>
Jean Louis <bugs@gnu.support> writes:
> * Bruno Barbier <brubar.cs@gmail.com> [2024-12-07 14:29]:
>> IIUC, all you would need is to use the documented API ('gptel-request')
>> and use its callback.
>
> I am still using my own function, it works well for me. My workflow is
> that I press C-F5 to invoke the prompt, and prompt takes whatever is
> in the region and it is added to it.
>
> It is of course possible to interpolate the response in any text, like
> in Org, I can of course enter it, just that I don't use Org too
> often. From meta level I may generate Org or just use snippets, I am
> using all kinds of markups which can be converted to each other.
>
> But I am curious how do you use AI with integration in Org?
>
> How do you use it in conversations?
>
> I can mark region of what customer said, I can say use 123 memory and
> answer to customer, and I get pretty good answer based on my previous
> AI memory. Is that what you mean?
>
> Or do you mean some kind of automatic conversation?
The package repository has a nice video that shows this package in
action. I think it will answer your questions better than I could
(I discovered this package recently; I just tried it out of curiosity,
no real needs).
>> But, if you don't need integration with org, conversations, multiple
>> backends, etc. , or just for fun, it makes sense to roll your own
>> solution.
>
> Multiple backends I have and it works well.
>
> But which other uses do you have?
I'm not sure I understand your question. I hope the video did answer
it for me ;)
Cheers,
Bruno
next prev parent reply other threads:[~2024-12-09 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 17:19 Including AI into Emacs Jean Louis
2024-12-06 18:16 ` Bruno Barbier
2024-12-06 22:18 ` Jean Louis
2024-12-07 9:32 ` Bruno Barbier
2024-12-07 10:30 ` Jean Louis
2024-12-07 11:29 ` Bruno Barbier
2024-12-09 21:06 ` Jean Louis
2024-12-09 22:56 ` Bruno Barbier [this message]
2024-12-10 8:03 ` Jean Louis
2024-12-10 10:37 ` Bruno Barbier
2024-12-10 14:27 ` Jean Louis
2024-12-06 18:22 ` Eli Zaretskii
2024-12-06 19:11 ` Basile Starynkevitch
2024-12-06 21:14 ` Jean Louis
2024-12-06 22:26 ` Jean Louis
2024-12-06 22:59 ` Christopher Howard
2024-12-06 23:21 ` Jean Louis
2024-12-10 10:45 ` Basile Starynkevitch
-- strict thread matches above, loose matches on Subject: below --
2024-12-06 17:22 Jean Louis
2024-12-06 18:25 ` Eli Zaretskii
2024-12-06 18:32 ` John Yates
2024-12-06 19:06 ` Jean Louis
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=675775ac.050a0220.1b7ef7.6fe2@mx.google.com \
--to=brubar.cs@gmail.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).