unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Yavner <jyavner@member.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: "Misunderstanding of the lambda calculus"
Date: Wed, 1 Feb 2006 10:01:39 -0500	[thread overview]
Message-ID: <200602011001.39899.jyavner@member.fsf.org> (raw)
In-Reply-To: <buoek2nmkfk.fsf@dhapc248.dev.necel.com>

> I think to anyone reasonably fluent in english, it's pretty clear that
> "archaic" was used quite deliberately in this case to mean "it
> sux0rz!1!" while avoiding explicitly confrontational language.  

Response was to change "archaic" to "older", which was still wrong but 
further discussions of the precise meaning of "archaic" are now 
obsolete.  The current problem (which has been solved but it's not 
clear yet whether the solution will stick) lies with the word 
"misunderstanding" and the mind-set it implies that "Scheme is what 
Lisp always should have been" (and more generally with the mind-set 
that it is acceptable to rewrite history so it points to your desired 
outcome).  Anyway, this isn't helping to get v22.1 out the door.

  reply	other threads:[~2006-02-01 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1F3FdP-0002xe-OW@monty-python.gnu.org>
2006-01-29 17:51 ` "Misunderstanding of the lambda calculus" Jonathan Yavner
2006-01-29 18:32   ` David Kastrup
2006-01-30 18:46     ` Richard M. Stallman
2006-01-30 19:28       ` David Kastrup
2006-01-31 18:03         ` Richard M. Stallman
2006-01-31 19:47           ` Kevin Rodgers
2006-01-31 20:09           ` Stefan Monnier
2006-02-01 19:38             ` Richard M. Stallman
2006-01-31 21:57           ` David Kastrup
2006-02-01  8:12             ` Alan Mackenzie
2006-02-01  8:52               ` David Kastrup
2006-02-01 10:40                 ` Miles Bader
2006-02-01 15:01                   ` Jonathan Yavner [this message]
2006-02-01 19:39             ` Richard M. Stallman
2006-01-29  5:42 Chong Yidong

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=200602011001.39899.jyavner@member.fsf.org \
    --to=jyavner@member.fsf.org \
    --cc=emacs-devel@gnu.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).