emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Attitude (was: Proposal: new default bindings for winner and windmov


From: Eli Zaretskii
Subject: Re: Attitude (was: Proposal: new default bindings for winner and windmove)
Date: Thu, 27 Jun 2024 08:16:14 +0300

> Date: Wed, 26 Jun 2024 20:38:35 +0000
> Cc: Stefan Kangas <stefankangas@gmail.com>,
>  Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> Hello, Stefan.

(Not really a "hello", is it?)

> Talking about minor proposals, I got the following message in
> *Async-native-compile-log*  in one of my development branches:
> 
> /home/acm/cc-mode.hg/cc-fonts.el: Error Wrong type argument: listp, #[(form) 
> (`(cdr (backquote-process ,form))) nil]
> 
> , which clearly has to do with your "minor proposal" to introduce a new
> type for interpreted functions.  I really can't be bothered at the moment
> to go through all the work of tracking this down, but would be grateful
> nevertheless if you would fix it.
> 
> By the way, did you get any approval for this change from the current
> maintainers, or did you just go ahead and commit it anyway?  I seem to
> remember you sweeping aside and ignoring my "disproportionately intense
> fire" on this matter, implying it would cause nobody extra work.

Alan, please drop this immature attitude.  It's unbecoming.

I have no idea what change you are talking about (as you "cannot be
bothered" to point it out, evidently), and I cannot try to reproduce
it myself (since you didn't tell how) or examine the backtrace (since
you haven't posted one), but in general, this is development, and
mistakes whether silly or serious, do happen.  When mistakes do
happen, we don't castigate our fellow developers, certainly not those
with Stefan's record, for any unintended consequences of their work.
Instead, we respectfully describe the problems with all the relevant
details and discuss how to fix the problems.

IOW, this is a cooperative community effort of developing software,
and I respectfully demand that each one of us behaves accordingly.
Anyone who misbehaves on my watch will be kindly asked to stop, or
else.

I now expect you to apologize and to post the details of the problem
(as a separate bug report).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]