From: Hank Greenburg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: hongyi.zhao@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Use ChatGPT in Emacs.
Date: Tue, 21 Feb 2023 06:13:02 +0000 [thread overview]
Message-ID: <4QyXQDBEX66eOm9G9GCMyzjRA7ym58z9tMpxe0jeLDLHiFt-SmoHBD6XsbyRr_sFmfFYjNQfLh6Wqkve4C3Foq4aQSJa8i3NtAW44RoNuoc=@protonmail.com> (raw)
In-Reply-To: <CAGP6POKkmAMqyZK9ETMgsCgf5KxaE3mGLu3_RE=m6E+78be46w@mail.gmail.com>
I can't exactly say for certain because I don't really know the difference between the OpenAI API and the ChatGPT API. Though I would suggest trying both to see how they fit your needs.
I've used the CodeGPT to help document code and explain functions, but it definitely isn't for a conversation.
-------- Original Message --------
On Feb 20, 2023, 23:41, Hongyi Zhao wrote:
> On Tue, Feb 21, 2023 at 10:23 AM Hank Greenburg wrote: > > I don't know of a ChatGPT implementation but there is an implementation of the OpanAI API which has code interaction if that's what you're looking for. > > https://github.com/emacs-openai/codegpt What's the difference between the one above and the one below? https://github.com/joshcho/ChatGPT.el Regards, Zhao > ------- Original Message ------- > On Monday, February 20th, 2023 at 2:30 AM, Hongyi Zhao wrote: > > > > > > > > Hi here, > > > > Does anyone here have the experience in using ChatGPT in Emacs? Any > > tips will be appreciated. > > > > Regards, > > Zhao > > -- > > Assoc. Prof. Hongsheng Zhao hongyi.zhao@gmail.com > > > > Theory and Simulation of Materials > > Hebei Vocational University of Technology and Engineering > > No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province
next prev parent reply other threads:[~2023-02-21 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 8:30 Use ChatGPT in Emacs Hongyi Zhao
2023-02-21 2:22 ` Hank Greenburg
2023-02-21 5:41 ` Hongyi Zhao
2023-02-21 6:13 ` Hank Greenburg via Users list for the GNU Emacs text editor [this message]
2023-02-21 14:20 ` Daniel Fleischer
2023-02-21 14:29 ` Hongyi Zhao
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='4QyXQDBEX66eOm9G9GCMyzjRA7ym58z9tMpxe0jeLDLHiFt-SmoHBD6XsbyRr_sFmfFYjNQfLh6Wqkve4C3Foq4aQSJa8i3NtAW44RoNuoc=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=hank.greenburg@protonmail.com \
--cc=hongyi.zhao@gmail.com \
/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).