all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Morally equivalent
Date: Mon, 17 Oct 2022 13:47:27 +0200	[thread overview]
Message-ID: <871qr6ek2t.fsf@gmail.com> (raw)
In-Reply-To: <87pmer9hrn.fsf@disroot.org>



> This should be:
>
> This is almost equivalent to (setf PLACE (cons NEWELT PLACE)),
> except that PLACE is evaluated only once (after NEWELT).
>
> Anyway, I enjoy occasionally finding things like "morally equivalent" in
> Emacs.

I agree. I think this kind of language actually beneficial, when it
helps in conveying the "intuition" behind a concept, using analogies
(this of course is nothing new, you almost certainly did this too if you
ever had to explain something to someone less experienced than you).

If we find this choice of word poor or misleading, that's actually very
good: it means we care for the quality of Emacs. But I would say that a
clarification would be just as good, without giving up the analogy:

"This is morally equvalent to [...], meaning that it is equal in all
practical sense, except that [...]"

(please correct me if I misunderstood something)

As a OCD guy, please let me tell you all: relax! :-)
It's very good to be passionate even about minor things. Not so much if
those become a division.

-- 
Alessandro Bertulli



  parent reply	other threads:[~2022-10-17 11:47 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  2:45 Morally equivalent John Haman
2022-10-16  2:55 ` Eduardo Ochs
2022-10-16  3:39 ` Michael Heerdegen
2022-10-16 14:29   ` [External] : " Drew Adams
2022-10-16 14:34     ` Heime
2022-10-16 14:42     ` Dr Rainer Woitok
2022-10-16 15:02       ` Drew Adams
2022-10-16 16:20         ` tomas
2022-10-16 19:27 ` Bob Newell
2022-10-16 19:43   ` [External] : " Drew Adams
2022-10-16 20:24     ` Bob Newell
2022-10-16 19:58   ` Christopher Dimech
2022-10-16 23:10     ` Michael Heerdegen
2022-10-16 23:17       ` Christopher Dimech
2022-10-16 23:32         ` Michael Heerdegen
2022-10-16 23:47           ` Eduardo Ochs
2022-10-17  1:13             ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-18 10:44               ` Dr Rainer Woitok
2022-10-17  0:00           ` Christopher Dimech
2022-10-17  0:10             ` Michael Heerdegen
2022-10-17  0:32               ` Christopher Dimech
2022-10-17  0:53                 ` Michael Heerdegen
2022-10-17  1:18                   ` Christopher Dimech
2022-10-17  4:52                 ` tomas
2022-10-17  5:27                   ` Christopher Dimech
2022-10-20 14:08                     ` Akib Azmain Turja
2022-10-20 16:24                       ` Christopher Dimech
2022-10-20 18:29                         ` tomas
2022-10-20 19:54                           ` Christopher Dimech
2022-10-17  4:49       ` Akib Azmain Turja
2022-10-17  6:44         ` Eli Zaretskii
2022-10-17  7:48           ` tomas
2022-10-17  9:15             ` Thibaut Verron
2022-10-17 23:01               ` Rudolf Adamkovič
2022-10-18  1:01               ` Michael Heerdegen
2022-10-18  1:07                 ` Emanuel Berg
2022-10-18  2:39                 ` Po Lu
2022-10-18  3:50                   ` Michael Heerdegen
2022-10-18 14:11                   ` Eli Zaretskii
2022-10-18 16:50                     ` Christopher Dimech
2022-10-18 23:11                     ` Emanuel Berg
2022-10-20 14:05                       ` Akib Azmain Turja
2022-10-20 17:14                         ` Christopher Dimech
2022-10-17 15:42             ` Christopher Dimech
2022-10-17 11:47         ` Alessandro Bertulli [this message]
2022-10-23 10:16 ` Will Mengarini
2022-10-24 14:46   ` Marcin Borkowski
2022-10-24 21:06     ` Emanuel Berg
2022-10-24 21:05   ` Emanuel Berg

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

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

  git send-email \
    --in-reply-to=871qr6ek2t.fsf@gmail.com \
    --to=alessandro.bertulli96@gmail.com \
    --cc=akib@disroot.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.