unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Tomáš Petit" <petitthomas34@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Enhancing ELisp for AI Work
Date: Tue, 17 Dec 2024 12:40:35 +0100	[thread overview]
Message-ID: <b10135c5-fe0d-4e5a-a64b-f14d299fb7d7@gmail.com> (raw)
In-Reply-To: <Z2FTzU7MK6LEeO1x@lco2>

I clearly haven't done my due diligence because I wasn't aware of those 
cool little projects. It certainly looks fun, not sure if Emacs Lisp 
will ever attract enough attention, although I would personally hope for 
Lisp (and its derivatives) to have a glorious return.

On 12/17/24 11:34 AM, Jean Louis wrote:
> * Tomáš Petit <petitthomas34@gmail.com> [2024-12-17 09:26]:
>> Right, that is of course entirely possible. I was thinking more along the
>> lines of projects like
>>
>> https://antik.common-lisp.dev/
>>
>> or
>>
>> https://github.com/melisgl/mgl
>>
>> and generally building the entire machinery natively in Elisp, for which I
>> find CL just a better option. But yeah, calling LLMs like that is viable as
>> well.
> Attempts in Emacs Lisp:
>
> narendraj9/emlib: Machine Learning in Emacs Lisp
> https://github.com/narendraj9/emlib
>
> Building and Training Neural Networks in Emacs Lisp
> https://www.scss.tcd.ie/~sulimanm/posts/nn-introduction.html
>



      reply	other threads:[~2024-12-17 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7290780.2375960.1734348492938.ref@mail.yahoo.com>
2024-12-16 11:28 ` Enhancing ELisp for AI Work Andrew Goh via Users list for the GNU Emacs text editor
2024-12-16 13:39   ` Jean Louis
2024-12-16 14:55   ` Tomáš Petit
2024-12-16 16:26     ` Jean Louis
2024-12-16 17:38     ` Jean Louis
2024-12-17  6:24       ` Tomáš Petit
2024-12-17 10:29         ` Jean Louis
2024-12-17 10:34         ` Jean Louis
2024-12-17 11:40           ` Tomáš Petit [this message]

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=b10135c5-fe0d-4e5a-a64b-f14d299fb7d7@gmail.com \
    --to=petitthomas34@gmail.com \
    --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).