From: Jean Louis <bugs@gnu.support>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Including AI into Emacs
Date: Sat, 7 Dec 2024 01:26:25 +0300 [thread overview]
Message-ID: <Z1N6EQ4TucwDA53-@lco2> (raw)
In-Reply-To: <c6bf7cc8ddc79c7b177fb6a087f30fb631437587.camel@starynkevitch.net>
* Basile Starynkevitch <basile@starynkevitch.net> [2024-12-06 22:12]:
> On of the issues is to define what is an open source AI system.
Without referring to common definitions, all of computing can be
considered artificial intelligence as it extends the mind functions
and memory of humans.
It is just a matter of development level to determine how far it may go.
At first, it might handle tasks like invoices. It could ask the user
every day, "Is there any invoice to enter?" If the user answers "Yes,"
the computer could then request the details.
On the next level, the computer may not need to ask the user but
could, through observation, understand that an invoice needs to be
entered. For example, it could recognize a customer's face through a
camera, identify the customer, and automatically generate an invoice.
All Emacs programs and essentially all programs in the world are forms
of artificial intelligence.
But now there are fantastic new developments where computers can
recognize pictures, generate new images through imagination, create
videos, correct text, and more easily understand what we think. This
is what we have been striving for.
And common users now can use it without tedious programming, and that
is huge advance.
It is like jumping from shell usage of Internet to graphics
browser. That happened in past, and is now happening with the AI
accessibility for all.
Of course, the notorious Emacs psychotherapist is predating all of the
modern chatbots.
--
Jean Louis
next prev parent reply other threads:[~2024-12-06 22:26 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 [this message]
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=Z1N6EQ4TucwDA53-@lco2 \
--to=bugs@gnu.support \
--cc=basile@starynkevitch.net \
--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).