unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Shane Mulligan <mullikine@gmail.com>
Cc: stefan@marxist.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Help building Pen.el (GPT for emacs)
Date: Sat, 17 Jul 2021 12:01:08 +0300	[thread overview]
Message-ID: <83im1948mj.fsf@gnu.org> (raw)
In-Reply-To: <CACT87JqMZ+pbVDQ-5gZHMsGcfm04CoeKZn6sY5yy+1rnxCimOQ@mail.gmail.com> (message from Shane Mulligan on Sat, 17 Jul 2021 14:36:15 +1200)

> From: Shane Mulligan <mullikine@gmail.com>
> Date: Sat, 17 Jul 2021 14:36:15 +1200
> Cc: Stefan Kangas <stefan@marxist.se>, Emacs developers <emacs-devel@gnu.org>
> 
> I think the end-goal should be to have a close collaboration with EleutherAI, who already have an
> open-source alternative to the Copilot model. It's called GPT-j.
> ελευθερία is a greek word that means Freedom. EleutherAI are open-sourcing language models.
> The problem is that there are very few people within EleutherAI using emacs and few people who can help. 

I'm not sure I understand what features in Emacs this could enable.
And the references you provided don't seem to answer this question (or
maybe the answer is buried deeper than I'm prepared to dig at this
point).  I understand that EleutherAI doesn't seem to support
programming at this point, only natural language (is that true?), but
that still means there could be any number of useful features where it
could help.  But what are they?  The stuff on the EleutherAI site is
oriented towards people who work in the machine learning domain, not
to programmers who design applications that could take advantage of
those capabilities, so it's not easy to understand what these
capabilities have in store for Emacs.

Thus, description of relevant Emacs features, whether existing or
imaginary, with enough details for us to be able to discuss that
intelligently, will be appreciated.  I don't think this discussion
will be meaningful without at least some idea of what we are trying to
accomplish.

> If you'd please excuse my speculative musings, emacs has 40 years of design waiting to be augmented with
> GPT3 and I believe that emacs is way ahead of the competition. It's a gold rush really.

Why do you think Emacs is better fitted to this than other editors?
It sounds like most of the processing is done server-side, so what
exactly is the significance of Emacs being the client?

> Name a package and I can name an augmentation.

Is this based on what these services (EleutherAI in particular) can
do, or are these just unrelated fantasies?  We need ideas based on
capabilities that exist, not on what could exist years from now.  AI
history is chock-full of ideas that didn't work out.

> Take 'erc' and make it the first IRC client to automatically translate all messages into any type of dialect --
> French, Klingon or Pirate.

How is this different from existing translation servers?

> Company-mode + GPT = Copilot.

I don't see how this is true.  Copilot is not just generalized
completion, and AFAIU doesn't fit into the presentation methods used
by Company.  What am I missing?

> Org-roam + GPT = A multiversal prose editor (https://github.com/socketteer/loom)

I couldn't understand what that does, looking at the above URL.  Any
details how it works and how it helps the writer?

> Org-brain + GPT = a mind map, which automatically generates and suggests nodes, then lets you talk to a
> chatbot tutor on any weird topic you can think of.

Does this capability really exist?

Thanks.



  reply	other threads:[~2021-07-17  9:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  4:36 Help building Pen.el (GPT for emacs) Shane Mulligan
2021-07-02 13:30 ` Jean Louis
2021-07-02 13:40 ` Jean Louis
2021-07-02 13:57 ` Jean Louis
2021-07-03  6:34   ` Shane Mulligan
2021-07-03 22:21     ` Jean Louis
2021-07-03 23:21       ` Arthur Miller
2021-07-03 23:42         ` Jean Louis
2021-07-12  3:24           ` Shane Mulligan
2021-07-17 23:53             ` Richard Stallman
2021-07-15 11:58 ` Stefan Kangas
2021-07-15 12:40   ` dick
2021-07-15 23:52   ` Shane Mulligan
2021-07-16  7:30     ` tomas
2021-07-17  0:33       ` Shane Mulligan
2021-07-17  7:54         ` tomas
2021-07-17  7:52       ` Jean Louis
2021-07-17  0:51   ` Richard Stallman
2021-07-17  2:36     ` Shane Mulligan
2021-07-17  9:01       ` Eli Zaretskii [this message]
2021-07-17  9:27         ` Shane Mulligan
2021-07-17 21:02           ` Shane Mulligan
2021-07-18  5:38             ` Jean Louis
2021-07-18  5:38             ` Jean Louis
2021-07-18  7:03               ` Eli Zaretskii
2021-07-18  8:00                 ` Shane Mulligan
2021-07-18  6:42             ` Eli Zaretskii
2021-07-17 21:35           ` Juri Linkov
2021-07-17 23:53       ` Richard Stallman

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=83im1948mj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mullikine@gmail.com \
    --cc=rms@gnu.org \
    --cc=stefan@marxist.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).