unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: schwab@linux-m68k.org, philipk@posteo.net,
	monnier@iro.umontreal.ca, me@eshelyaron.com, emacs-devel@gnu.org
Subject: Re: [External] : Re: Question about eval and compile-command
Date: Fri, 04 Aug 2023 08:40:05 +0300	[thread overview]
Message-ID: <83jzubwekq.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54889032D8B4CB2864A57218F308A@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Thu, 3 Aug 2023 21:35:39 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>,
>  Eshel Yaron <me@eshelyaron.com>,
>  "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Thu, 3 Aug 2023 21:35:39 +0000
> 
> > > In retrospect, shouldn't the type be be a string or a function?
> > 
> > Not a function, but a form.
> 
> A string is a form too...

Methodologically, it is not good to rely on this, because many Emacs
users will not realize that.  We never use "form" when we talk about
strings, for that very reason.

Using mathematical rigor when writing software documentation is almost
never a good idea, in practice.



  reply	other threads:[~2023-08-04  5:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  9:29 Question about eval and compile-command Eshel Yaron
2023-08-03  9:56 ` Eli Zaretskii
2023-08-03 15:14   ` Stefan Monnier
2023-08-03 16:23     ` Eshel Yaron
2023-08-03 17:24       ` Stefan Monnier
2023-08-03 20:02     ` Philip Kaludercic
2023-08-03 20:39       ` Stefan Monnier
2023-08-03 21:14       ` Andreas Schwab
2023-08-03 21:35         ` [External] : " Drew Adams
2023-08-04  5:40           ` Eli Zaretskii [this message]
2023-08-04  6:51           ` Andreas Schwab
2023-08-04  7:00             ` Philip Kaludercic

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=83jzubwekq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=me@eshelyaron.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=schwab@linux-m68k.org \
    /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).