From: Basile Starynkevitch <basile@starynkevitch.net>
To: Jean Louis <bugs@gnu.support>, Emacs Tangents <help-gnu-emacs@gnu.org>
Subject: Re: Including AI into Emacs
Date: Fri, 06 Dec 2024 20:11:49 +0100 [thread overview]
Message-ID: <c6bf7cc8ddc79c7b177fb6a087f30fb631437587.camel@starynkevitch.net> (raw)
In-Reply-To: <61ffb7417fcfe6fc0c1291aa53d1398b.support1@rcdrun.com>
On Fri, 2024-12-06 at 20:19 +0300, Jean Louis wrote:
> Today, I’ve noticed that there are many free software projects that
> use artificial intelligence, or AI for short. These projects are
> created by developers all around the world who want to make useful
> tools available to everyone. AI can help solve complex problems,
> automate tasks, and improve the way we interact with technology. It’s
> exciting to see so many people contributing to these projects and
> making AI more accessible to everyone.
>
> 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.
>
> I am using AI every day, and will soon provide references on how to
> use it self-contained, as every user can download it and run it on
> their own computers.
On of the issues is to define what is an open source AI system.
Is https://clipsrules.net/ an AI system? (On Linux you could run it
from GNU emacs)?
Can https://github.com/RefPerSys/RefPerSys be extended (or the basis
of) to become an AI system? It is GPLv3+ licensed?
Both software are open source... See also http://refpersys.org/
Regards from near Paris in France....
--
Basile STARYNKEVITCH <basile@starynkevitch.net>
8 rue de la Faïencerie
92340 Bourg-la-Reine, France
http://starynkevitch.net/Basile & https://github.com/bstarynk
next prev parent reply other threads:[~2024-12-06 19:11 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 [this message]
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=c6bf7cc8ddc79c7b177fb6a087f30fb631437587.camel@starynkevitch.net \
--to=basile@starynkevitch.net \
--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).