From: luigi scarso via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: luigi scarso <luigi.scarso@gmail.com>
Subject: Re: [NTG-context] knuth
Date: Thu, 1 Jun 2023 12:32:02 +0200 [thread overview]
Message-ID: <CAG5iGsArdH6W3ZNmHDdzVntqcgxXtayXSUazGnxexpaPk3rEAw@mail.gmail.com> (raw)
In-Reply-To: <4d6bfac1-1ce5-fff0-9309-b07b6879eb76@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1401 bytes --]
On Thu, 1 Jun 2023 at 11:45, Hans Hagen via ntg-context <ntg-context@ntg.nl>
wrote:
> Hi,
>
> Probably some on this list already checked how well chatgpt answers
> questions about domains one knows well and then probably noted that in
> spite of impressive wording, one can run into quite incorrect answers.
>
> One can get really stupid responses about tex and friends, but also can
> get impressive exmapled when asked for. (I'm still planning a wrap up of
> some.)
>
> That said, one should read:
>
> https://cs.stanford.edu/~knuth/chatGPT20.txt
>
> and this makes a pretty nice new sample file:
>
> It's amazing how the confident tone lends credibility to all of that
> made-up nonsense. Almost impossible for anybody without knowledge
> of the book to believe that those "facts" aren't authorititative
> and well researched.
>
you can happily include the email that I have sent to you that declares
that *you* are the author of MFlua
and *I* have nothing to do with it (chatgpt3: as far as I know, the
overall number of users+developers of MFLua in the entire solar system is
exactly 1 -- me -- at least from 10 years) .
For a moment I was even convinced that it was true.
On the other hand, I am pretty sure that it will be able to
generate perfect lualatex files for articles, reports, and later books.
How and when it's more a matter of interest rather than capabilities.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2038 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-06-01 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 9:44 Hans Hagen via ntg-context
2023-06-01 10:32 ` luigi scarso via ntg-context [this message]
2023-06-01 11:49 ` Floris van Manen via ntg-context
2023-06-02 7:27 ` BPJ via ntg-context
2023-06-02 7:58 ` Hans Hagen via ntg-context
2023-06-02 21:07 ` Carlos via ntg-context
2023-06-04 21:57 ` Berend de Boer via ntg-context
2023-06-05 13:09 ` Alan Braslau via ntg-context
2023-06-05 14:20 ` Carlos via ntg-context
2023-06-05 14:50 ` luigi scarso via ntg-context
2023-06-05 15:22 ` Alan Braslau via ntg-context
2023-06-05 16:07 ` Carlos via ntg-context
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG5iGsArdH6W3ZNmHDdzVntqcgxXtayXSUazGnxexpaPk3rEAw@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=luigi.scarso@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 NNTP newsgroup(s).