From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master baf1a7a4a0: Turn gv-synthetic-place into a function
Date: Fri, 23 Sep 2022 18:54:54 +0300 [thread overview]
Message-ID: <83pmfmozld.fsf@gnu.org> (raw)
In-Reply-To: <lyfsgi8aw5.fsf@Lumet.home> (message from Howard Melman on Fri, 23 Sep 2022 09:42:50 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Fri, 23 Sep 2022 09:42:50 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Howard Melman <hmelman@gmail.com>
> >> Date: Thu, 22 Sep 2022 15:55:03 -0400
> >>
> >> For me, I'm still not completely clear if "generalized
> >> variable" is exactly the same as "place" and if "generalized
> >> variable form" is the same as "place form". That's what I'd
> >> like to see clarity on and if they are the same, just use
> >> one term.
> >
> > They are the same thing.
>
> Thanks.
>
> Then I think using just one term is clearer and I agree with
> Lars about avoiding "place" as much as possible. I think GV
> would be a clearer parameter name than PLACE.
That ship has sailed, unfortunately. Where were you (and Lars) when
this terminology was introduced and I tried to find some better
alternatives, but was voted down?
next prev parent reply other threads:[~2022-09-23 15:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 16:13 master baf1a7a4a0: Turn gv-synthetic-place into a function Eli Zaretskii
2022-09-19 6:16 ` Michael Heerdegen
2022-09-19 11:38 ` Eli Zaretskii
2022-09-20 7:28 ` Michael Heerdegen
2022-09-20 7:50 ` Emanuel Berg
2022-09-20 11:19 ` Eli Zaretskii
2022-09-20 14:36 ` Michael Heerdegen
2022-09-20 16:27 ` Eli Zaretskii
2022-09-21 5:40 ` Michael Heerdegen
2022-09-21 14:19 ` Eli Zaretskii
2022-09-21 8:35 ` Emanuel Berg
2022-09-21 8:32 ` Emanuel Berg
2022-09-21 13:52 ` Michael Heerdegen
2022-09-21 14:20 ` Stefan Monnier
2022-09-21 15:31 ` Eli Zaretskii
2022-09-21 16:14 ` Stefan Monnier
2022-09-22 10:47 ` Lars Ingebrigtsen
2022-09-22 11:53 ` Michael Heerdegen
2022-09-22 14:27 ` Michael Heerdegen
2022-09-22 16:30 ` Augusto Stoffel
2022-09-22 17:27 ` [External] : " Drew Adams
2022-09-22 17:47 ` Michael Heerdegen
2022-09-23 15:07 ` Lars Ingebrigtsen
2022-09-22 12:26 ` Yuri Khan
2022-09-22 14:11 ` Howard Melman
2022-09-22 16:45 ` Eli Zaretskii
2022-09-22 19:55 ` Howard Melman
2022-09-23 6:19 ` Eli Zaretskii
2022-09-23 13:42 ` Howard Melman
2022-09-23 15:49 ` Stefan Monnier
2022-09-23 18:05 ` Howard Melman
2022-09-23 15:54 ` Eli Zaretskii [this message]
2022-09-23 18:11 ` Howard Melman
2022-09-23 19:00 ` Eli Zaretskii
2022-09-23 9:41 ` Michael Heerdegen
2022-09-23 10:53 ` Eli Zaretskii
2022-09-23 17:26 ` Emanuel Berg
2022-09-22 10:56 ` Michael Heerdegen
2022-09-30 23:18 ` Emanuel Berg
2022-09-30 23:30 ` Emanuel Berg
2022-09-19 12:06 ` Stefan Monnier
2022-09-20 7:22 ` Michael Heerdegen
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=83pmfmozld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hmelman@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.
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).