From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones Date: Thu, 21 Sep 2023 08:22:45 -0700 Message-ID: References: <5023567.7IPSAfTSoR@ravel> <83cz3qtyno.fsf@gnu.org> <4916306.ghxcXLinNW@ravel> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31700"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 63072@debbugs.gnu.org To: Olivier Certner Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 21 17:24:16 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qjLXM-0007zZ-30 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 21 Sep 2023 17:24:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjLX0-0007Wt-TI; Thu, 21 Sep 2023 11:23:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qjLWz-0007WQ-2p for bug-gnu-emacs@gnu.org; Thu, 21 Sep 2023 11:23:53 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qjLWy-0007dc-On for bug-gnu-emacs@gnu.org; Thu, 21 Sep 2023 11:23:52 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qjLX8-0008ND-G0 for bug-gnu-emacs@gnu.org; Thu, 21 Sep 2023 11:24:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 21 Sep 2023 15:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63072 X-GNU-PR-Package: emacs Original-Received: via spool by 63072-submit@debbugs.gnu.org id=B63072.169530978732089 (code B ref 63072); Thu, 21 Sep 2023 15:24:02 +0000 Original-Received: (at 63072) by debbugs.gnu.org; 21 Sep 2023 15:23:07 +0000 Original-Received: from localhost ([127.0.0.1]:34642 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qjLWF-0008LS-Az for submit@debbugs.gnu.org; Thu, 21 Sep 2023 11:23:07 -0400 Original-Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]:48483) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qjLWB-0008Kx-3L for 63072@debbugs.gnu.org; Thu, 21 Sep 2023 11:23:06 -0400 Original-Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2c108e106f0so18794711fa.1 for <63072@debbugs.gnu.org>; Thu, 21 Sep 2023 08:22:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695309767; x=1695914567; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=8YD1HidvavPJc/XA0GjFG7aYxRqL34XLyUZrl5JbSHk=; b=WaTCDuWlPLpKluVTsrnZYxrjY7fG+Xj3eb0HRGt/jtgbrAxkhpH1BIxNLA8rlc04wB uvIl3QM5NfjVIvsnjT49ang2oezikRB6VIHPpYlNsbaKNYANmdpxvjA5OnoR3IrXgGq9 UzHS0fz0lxtRzLW4jE0LIQoBgcCvaZ9zHzSVq9sp67fE0oxMtWX+91BY2DkQG53gfFUH p702xm3V6ntmL9+SUjPWSkZF+ovomtyfkjJEsUVjHoe2RmjFyuod4ofE3nMR4gAhy98I NFv8eeEukeokRBmDL3zLfWiRjjXAFDvJxvOfYEaH0gB6OpHcKtgwmwv13okJrr8nlZze gByA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695309767; x=1695914567; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=8YD1HidvavPJc/XA0GjFG7aYxRqL34XLyUZrl5JbSHk=; b=V4YyhrzEoi6WLYeKR3pl+w8VhYHChn+2fmwFdDSuaD79GLko7e4W3eBlO3tkThbADZ 9Nq8VSW8w7tC8h6t1L2f0E2qV8nBGkosi09EY5ibjGFT+/xBXuTsvEhpvUMngHzAe4O/ jmMVK0cWd8O9UBxZRi/MhRTmZ17aZJL6tjdFSsVGXhtjkruQJ8b1HHGpR+hWuVPXJbd6 l73p4s/E9FlV86/REdFH4+8/7SAUYtssYt3p9wCKYVj6sj4z6k3Fbn5F8kSUsDxdKStQ y7TwzdKXcOoWYOnVI1v3JSgs081jqKTMuo5fJBoVQa5AbKA4l3yMsvZUWyn8AX2bxlFq E4Wg== X-Gm-Message-State: AOJu0YxssilA1adGfKToaFM6ascQe/+4tynb/mrSGhglstFFB65fpby7 kV7+C18tLOvsEE3G7oA3eZuYWO5Ss52wEgdaYbI= X-Google-Smtp-Source: AGHT+IH67ogEB8NGxlbNTuSzg52J17wzmiGb31YzcWRaqlbsYkXXHb7/FQqOKg1bWnwoBschZjPYJ3CfOZlKwx3P7/A= X-Received: by 2002:a2e:a404:0:b0:2b6:a827:164f with SMTP id p4-20020a2ea404000000b002b6a827164fmr5265536ljn.10.1695309766623; Thu, 21 Sep 2023 08:22:46 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 21 Sep 2023 08:22:45 -0700 In-Reply-To: <4916306.ghxcXLinNW@ravel> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:270999 Archived-At: Hi Olivier, Olivier Certner writes: > I have been using a complete version since a short time after creation of this > bug, but haven't had much time to work on upstreaming that, and probably won't > in the coming weeks. > > Refining the new styles to cope with some corner cases unfortunately required > a couple of new fixup functions, and minor changes in CC mode that may be > controversial, such as setting all variables as buffer-local when `c-style- > variables-are-local-p' is true, or working around the weird behavior of CC > mode concerning `for' clauses (this one surely proved controversial, see > #63286; it is possible to do away with a lineup function as a workaround, at > the price of elegance and performance, but this is not the current setup I'm > running so coming back to a vanilla one will require more work on my part). > > Additionally, given the fallout of #63286, I think you can understand I'm not > contemplating a new discussion with the CC mode maintainer with great joy. In > the context of this bug, being looked down on by someone who provided mostly > wrong technical answers and that otherwise showed a pronounced tendency to > spread FUD is not exactly my conception of an enriching collaboration. > Certainly, my final answer there wasn't neat, but "as you sow, so shall you > reap". > > More generally, I've found that interacting with upstream often wastes way too > much time than it should simply because people don't really read carefully > what they have been sent and/or have trouble with the nuances, sometimes even > insisting on focusing on mostly irrelevant details. You don't have to search > far for an example, look no further than this bug's initial discussion. I > unfortunately know of several other examples, half of which I've personally > not been involved in at all. At a higher level, to put it bluntly (and > exaggerating in order to make sure the point gets through), a sample of > discussions in the mailing list in the past months gives more the impression > of a clique wanting to preserve their own way of working/thinking rather than > genuinely addressing the concerns of other users and developers (yes, most of > them are "outsiders", which is the reason why some "insiders" apparently think > they know better even concerning their own requests). Besides the atmosphere > that all this creates, more practically I don't have much time to contribute > here so when I do so it's a significant effort on my part. In exchange, I > *demand* that others be respectful for that by making the effort of carefully > reading and understanding what I'm writing, and trying to stay to the point as > much as possible. Else, I'm simply likely to loose interest and keep all my > Emacs developments and customizations for myself (in 20+ years, they are > numerous). I'm hoping your nomination as a co-maintainer will help improve > this situation, so I'm sorry to have had to drop that on you. I understand your position, and let me be the first to acknowledge that email can be a challenging medium to work in. From my point of view, I can only urge everyone to try work together even when there are or have been misunderstandings. I also urge people to give each other the benefit of the doubt. If someone asks a question, more likely than not it is a genuine question. Emacs contributors come from all types of backgrounds, and there's always a chance that someone is lacking the necessary context to understand what is being said. Or they didn't yet have their morning coffee... you know, shit happens. Let's be patient with each other when we make mistakes or oversee some important aspect. The GNU Kind Communication Guidelines is recommended reading as a broad outline of the kind of environment we try to foster (even though we don't always succeed, admittedly): https://www.gnu.org/philosophy/kind-communication.html My goal is that we can find a way to work constructively and move forward towards our common goal of improving Emacs. That would be the best outcome. If we fail, let's try again, and let's try to do better. In my experience, we usually get the best result if we focus on the specifics of the issue at hand. > I've not given up on the idea to finally be able to upstream all that, but it > most likely won't happen in the short term (next weeks/a few months) for time > constraints. Also, I hope that, when the time comes, the next interactions > will be treated with the goodwill and productivity I expect (and which some of > the "core" members have already shown they are largely capable of to me). > > So this bug is effectively on hold on my side. I would simply leave it open > for the time being, but then it's your call on how you want to manage that > administratively. If you prefer to have a clean backlog, you can close it and > I'll re-open it later when I'm ready. I suggest keeping the bug open for now, as a reminder about this work. There is no rush, but I'm looking forward to seeing your patch once you can find the time to work on it. Thanks again for your contributions.