ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Mon, 5 Jun 2023 16:50:53 +0200	[thread overview]
Message-ID: <CAG5iGsBZdFstCN=Z_KiHGO9bEkFguOc6WTkYXSm7RXt_Uf6YXQ@mail.gmail.com> (raw)
In-Reply-To: <74549341-ee0c-13ea-82df-4a1156b6c6da@icloud.com>


[-- Attachment #1.1: Type: text/plain, Size: 1306 bytes --]

On Mon, 5 Jun 2023 at 15:18, Alan Braslau via ntg-context <
ntg-context@ntg.nl> wrote:

>
> On 04/06/23 04/06/23, 15:57, Berend de Boer via ntg-context wrote:
> >> 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.
> >
> > I've been using it for ConTeXt, and to be honest, it works amazingly
> > well. It hallucinates sometimes, but it's such a time saver.
>
> Maybe someone should try asking it to write documentation/manuals?
>
> As a teacher, we are accustomed to seeing Google/Wikipedia/etc.
> cut-and-paste nonsense; now, this nonsense appears more polished, and
> our students are none the wiser. Saves them time, too! ;-)
>
> Who said: "the best way to economize thought is not to think at all"?
>


not all is bad: sometimes a textual description can replace a formalized
notation, e.g.
https://fosstodon.org/@tao@mathstodon.xyz/110250604086213386
I can imagine similar examples with tables.
Of course a very high level text is often ambiguous (as some kind of
formalized grammars, after all)
but  the example shows that in these cases  it is better to fix something
already almost ok than  to typeset it from scratch.

--
luigi

[-- Attachment #1.2: Type: text/html, Size: 1919 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
___________________________________________________________________________________

  parent reply	other threads:[~2023-06-05 14:51 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
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 [this message]
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='CAG5iGsBZdFstCN=Z_KiHGO9bEkFguOc6WTkYXSm7RXt_Uf6YXQ@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).