From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: 57440@debbugs.gnu.org
Subject: bug#57440: [patch] Guile manual has incorrect history on the name
Date: Fri, 11 Nov 2022 22:57:32 +0100 [thread overview]
Message-ID: <877d01nof7.fsf@web.de> (raw)
In-Reply-To: <87bks64kbq.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
> --- 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
> --
Is this good to go? I can nowadays push the change myself, so a simple
lgtm gets this into Guile :-)
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 --]
prev parent reply other threads:[~2022-11-11 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 21:32 bug#57440: Guile manual has incorrect history on the name Lee Thomas
2022-08-26 23:43 ` bug#57440: [patch] " Dr. Arne Babenhauserheide
2022-08-27 3:43 ` Lee Thomas
2022-10-01 13:53 ` bug#57440: " Ludovic Courtès
2022-12-10 17:36 ` Dr. Arne Babenhauserheide
2022-11-11 21:57 ` Dr. Arne Babenhauserheide [this message]
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=877d01nof7.fsf@web.de \
--to=arne_bab@web.de \
--cc=57440@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).