From: Alan Mackenzie <acm@muc.de>
To: Christopher Dimech <dimech@gmx.com>
Cc: emacs-devel@gnu.org
Subject: Re: My resignation from Emacs development
Date: Thu, 21 Nov 2024 10:29:30 +0000 [thread overview]
Message-ID: <Zz8Lii0u9J6RjsFL@MAC.fritz.box> (raw)
In-Reply-To: <trinity-0dbc3b7e-bda7-42ad-801c-b236ba48cc30-1732119800541@3c-app-mailcom-bs01>
Hello, Christopher.
On Wed, Nov 20, 2024 at 17:23:20 +0100, Christopher Dimech wrote:
> The claim that using free software or its associated names constitutes
> aggression is fundamentally flawed. Aggression involves hostile actions
> meant to cause harm, and using names in a way not intended by their
> original authors is neither violent nor malicious.
There are forms of aggression which don't use fists or guns.
> One of the key principles of free software is that software should be
> modifiable, and free to use in any context. Restricting how names are
> used run counter to the ethos to empower users and developers, not to
> limit or control their language or expressions.
Fine. I put it to you that if somebody were to take the name
dimech@gmx.com and prevent it connecting up with your inbox, you would
be somewhat unhappy.
> Although the approach should be reconsidered, there should be some
> thoughtful conversation among the community. Avoiding tones of contempt
> or disregard for the foundations laid by previous contributors.
How very considerate and reasonable of you. The time for "thoughtful
conversation" around the current matter is long past. You should
perhaps address your comments to those who bypass and evade "thoughtful
conversation" at the appropriate time.
> For instance, I agree with you that ("\\.myc\\'" . c-mode) in auto-mode-alist
> should mean C Mode. Although C Mode would mean the emacs preferred mode.
> Still, your mode name can be changed for those who want to apply an alternative
> mode. Changing the mode should be a straightforward thing.
C Mode has been called that for a long time, possibly longer than you
have been called Christopher Dimech. As far as I'm concerned, it's
going to keep its name.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2024-11-21 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 15:13 My resignation from Emacs development Alan Mackenzie
2024-11-20 15:34 ` Eli Zaretskii
2024-11-20 16:23 ` Christopher Dimech
2024-11-21 6:22 ` Gerd Möllmann
2024-11-21 10:05 ` Christopher Dimech
2024-11-21 11:23 ` Gerd Möllmann
2024-11-21 11:40 ` Eli Zaretskii
2024-11-21 10:29 ` Alan Mackenzie [this message]
2024-11-21 12:26 ` Christopher Dimech
2024-11-20 16:42 ` Alfred M. Szmidt
2024-11-20 17:04 ` tomas
2024-11-20 21:56 ` Dmitry Gutov
2024-11-21 2:28 ` Stefan Kangas
2024-11-21 12:34 ` Tree-sitter maturity (was: My resignation from Emacs development) Peter Oliver
2024-11-21 13:01 ` My resignation from Emacs development Alan Mackenzie
2024-11-21 13:48 ` Eli Zaretskii
2024-11-21 14:29 ` Alfred M. Szmidt
2024-11-21 16:29 ` Alan Mackenzie
2024-11-21 5:59 ` Gerd Möllmann
2024-11-21 13:39 ` Andrea Corallo
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=Zz8Lii0u9J6RjsFL@MAC.fritz.box \
--to=acm@muc.de \
--cc=dimech@gmx.com \
--cc=emacs-devel@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.
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).