From: dick <dick.r.chiang@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Shane Mulligan <mullikine@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Help building Pen.el (GPT for emacs)
Date: Thu, 15 Jul 2021 08:40:08 -0400 [thread overview]
Message-ID: <87a6mnu4wn.fsf@dick> (raw)
In-Reply-To: <CADwFkm=cN4W0Mgo_hYgwWgddoe=cXj5+WYJWnAHZmmd+rd7gKw@mail.gmail.com> (Stefan Kangas's message of "Thu, 15 Jul 2021 13:58:11 +0200")
SK> Could you briefly elaborate on the capabilities of "GPT-3+vscode" and why
SK> you think it is an Emacs killer?
“If the people believe there’s an imaginary river out there, you don’t tell
them there’s no river there. You build an imaginary bridge over the imaginary
river.” -- Nikita Kruschev
The Copilot brouhaha takes the premature optimization and pointless
speculation endemic to emacs-devel to another level.
next prev parent reply other threads:[~2021-07-15 12:40 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 [this message]
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
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=87a6mnu4wn.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mullikine@gmail.com \
--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).