From: Christopher Howard <christopher@librehacker.com>
To: Jean Louis <bugs@gnu.support>
Cc: Emacs Tangents <help-gnu-emacs@gnu.org>
Subject: Re: Including AI into Emacs
Date: Fri, 06 Dec 2024 13:59:03 -0900 [thread overview]
Message-ID: <87msh8ctag.fsf@librehacker.com> (raw)
In-Reply-To: <61ffb7417fcfe6fc0c1291aa53d1398b.support1@rcdrun.com> (Jean Louis's message of "Fri, 06 Dec 2024 20:19:47 +0300")
Jean Louis <bugs@gnu.support> writes:
> I believe it would be really beneficial to include AI into GNU
> Emacs. Emacs is already a powerful tool, but adding AI features could
> make it even better. For example, AI could help with writing by
> suggesting improvements or catching mistakes. It could also assist
> with coding by providing smart autocomplete options or debugging
> help. These features would make Emacs more efficient and
> user-friendly, helping users get their work done faster and with fewer
> errors.
>
Could you clarify what you mean exactly but "including AI into GNU Emacs"? I know for sure I don't want Emacs sending information about my system, or questions that I have about Emacs or my project, off to some company's LLM chat system, or however that works exactly. I do not want to become dependent on some remote computer program or AI in order to be able to write code or figure out how Emacs works.
I'm certain interested in running tools locally (same computer, or my network) that help me with "suggesting improvements, catching mistakes", etc. Do you need something massive like ChatGPT to accomplish that, or just some Emacs-centric expert systems? Or maybe something like MycroftAI, running locally?
--
Christopher Howard
next prev parent reply other threads:[~2024-12-06 22:59 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
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 [this message]
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=87msh8ctag.fsf@librehacker.com \
--to=christopher@librehacker.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).