From: Michael Heerdegen <michael_heerdegen@web.de>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Morally equivalent
Date: Mon, 17 Oct 2022 01:32:58 +0200 [thread overview]
Message-ID: <87h703e445.fsf@web.de> (raw)
In-Reply-To: <trinity-b83001c0-5ee0-411c-a7ed-5eda6060fe0d-1665962276424@3c-app-mailcom-bs10> (Christopher Dimech's message of "Mon, 17 Oct 2022 01:17:56 +0200")
Christopher Dimech <dimech@gmx.com> writes:
> The problem was about the wording, if it turns out Stefan wrote it, then
> he is not above anybody else. The problem is that in some important ways,
> things are not precise.
Nothing in human language is precise. For me it was precise enough to
understand the meaning perfectly.
> And users do not like that.
I liked it. Most people like it much less when Stefan tries to be more
precise.
Honestly, the only problem with that wording is that it might make
people wonder whether it is some sort of technical term, which it is not
really, so it can potentially confuse people.
Michael.
next prev parent reply other threads:[~2022-10-16 23:32 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 [this message]
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
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
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=87h703e445.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@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).