unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: 59204@debbugs.gnu.org
Subject: bug#59204: [PATCH] small history doc change: the name change was suggested by Lee Thomas
Date: Fri, 11 Nov 2022 22:06:17 +0100	[thread overview]
Message-ID: <87fsepnp2g.fsf@web.de> (raw)


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

Hi,

since I collected references from various newsgroups, I’d like to
suggest this change to the history part of the docs: the name change to
Guile was suggested by Lee Thomas.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-doc-Lee-Thomas-suggested-the-name-change.patch --]
[-- Type: text/x-patch, Size: 2659 bytes --]

From e00afe1654773ac4e5eebe2e3ec4f0186c23d1f9 Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide <arne_bab@web.de>
Date: Sat, 27 Aug 2022 01:57:57 +0200
Subject: [PATCH] doc: Lee Thomas suggested the name change.

See (1994-11-04) https://groups.google.com/g/gnu.misc.discuss/c/0VtEf1fgEJk/m/IMBs2o-ftrgJ
> If GEL and GUL and GLUE don't work for the name of the scripting
> language, how about:
>
> GUILE - GNU's Universal Interpreted Language Extension
>
> (This also implies Scheme-ing, and means that the GNU's Universal
> Interpreted Language Developers would be part of a ...)
> --
> Lee Thomas

and (1994-11-22) https://groups.google.com/g/gnu.misc.discuss/c/9pD9yVoRYFw/m/0z7SLYbx8loJ
> Why "GUILE"? (GNU's Universal Interpreted Language Extension)
> Two additional reasons:
>
> 1. It does not give deliberate offense to Dr. Ousterhout or his
> supporters, thereby allowing the warring factions to eventually
> make peace (along with some others, perhaps - Gloria's 'Usband Is
> Linguistically Educated) and get back to work.
> 2. By pronunciation it offers appreciation to one of the co-inventors
> of Scheme. (Maybe a library package could be named "Scheme User
> Supported System Macros And Native-code"? OK, that's a stretch ...)
> --
> Lee Thomas,

and https://groups.google.com/g/comp.lang.scheme/c/X5GrLVAvGLU/m/Xk11xCrbzCcJ
> A while back, I started calling the language being built by the GNU Project
> GEL. It turns out that GEL is a trademark of Sybase Inc. Therefore,
> we must choose a new name. Please do not refer to the GNU language
> as GEL.
>
> My favorite proposed name, posted recently to comp.lang.scheme, is GUILE.
> I like the name, because i think programmers should be encouraged to use
> GUILE when writing programs. The name may change yet again; but for now,
> please refer to the GNU language as GUILE.
>
> -t
---
 doc/ref/history.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/ref/history.texi b/doc/ref/history.texi
index d351455a5..60d839ac3 100644
--- a/doc/ref/history.texi
+++ b/doc/ref/history.texi
@@ -69,7 +69,7 @@ the argument was that eventually when GEL became more capable, it
 could gain the ability to execute other languages, especially Emacs
 Lisp.
 
-Due to a naming conflict with another programming language, Jim Blandy
+Due to a naming conflict with another programming language, Lee Thomas
 suggested a new name for GEL: ``Guile''. Besides being a recursive
 acronym, ``Guile'' craftily follows the naming of its ancestors,
 ``Planner'', ``Conniver'', and ``Schemer''. (The latter was truncated
-- 
2.38.0


[-- Attachment #1.3: Type: text/plain, Size: 101 bytes --]


Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

             reply	other threads:[~2022-11-11 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 21:06 Dr. Arne Babenhauserheide [this message]
     [not found] ` <handler.59204.B.166820310311219.ack@debbugs.gnu.org>
2022-11-11 21:46   ` bug#59204: Duplicate of bug#57440 — sorry for that, I still had it in my patch list and saw that it did not get killed on pull+rebase so I thought I had forgotten to send it Dr. Arne Babenhauserheide

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsepnp2g.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=59204@debbugs.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.
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).