From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Danny Freeman Newsgroups: gmane.emacs.devel Subject: Re: Brand new clojure support in Emacs ;-) Date: Fri, 01 Sep 2023 09:34:02 -0400 Message-ID: <87pm32hutl.fsf@dfreeman.email> References: <87il9kksqz.fsf@dfreeman.email> <87a5uw9ivs.fsf@posteo.net> <87ttt42gna.fsf@dfreeman.email> <87wmy080kn.fsf@posteo.net> <83v8djcydl.fsf@gnu.org> <87350ndquw.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87zg2hsyrd.fsf@dfreeman.email> <87h6ontwfv.fsf@posteo.net> <835y4ucrz3.fsf@gnu.org> <831qficgin.fsf@gnu.org> <87ttsehwab.fsf@dfreeman.email> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21334"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Dmitry Gutov , Richard Stallman , =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= , emacs-devel To: Lynn Winebarger Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 01 15:45:16 2023 Return-path: Envelope-to: ged-emacs-devel@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 1qc4SZ-0005Hp-Fx for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Sep 2023 15:45:15 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qc4Rx-0005Rm-OP; Fri, 01 Sep 2023 09:44:37 -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 1qc4Rt-0005RX-BC for emacs-devel@gnu.org; Fri, 01 Sep 2023 09:44:34 -0400 Original-Received: from out-238.mta1.migadu.com ([95.215.58.238]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qc4Rp-0001kZ-Ii for emacs-devel@gnu.org; Fri, 01 Sep 2023 09:44:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dfreeman.email; s=key1; t=1693575866; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XY0VxurjGSf53//xpxyhU8LnU8yWre1CRzLE+rV+dls=; b=Ly+hgxkhEahKHSh4KK/ykSP1iyhYaF0hoyfdAeQqAKRxA9bKuqNqW3qdEHwjWk/88pRevw fyKH40Lq9vQup8lNh6OYQ/rhpIb/hzOAKB+cVNd7IN9kfl5rLSFwZVYhnBuvjwAv9K4atO c/KqQE/4qYSECHEgN+yISJiumoUaxRM= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-reply-to: X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=95.215.58.238; envelope-from=danny@dfreeman.email; helo=out-238.mta1.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309786 Archived-At: Lynn Winebarger writes: > I don't think using the term "hijacking" is productive. Maybe a better term is "taking over", "co-opting", I don't know. I am trying to be productive about this. > The GNU emacs > developers could well say that using a standard functional name like > "clojure-mode" with no intent to contribute it to the core was the > "hijacking", or perhaps namespace-squatting. It would be different for > "cider" or another non-standard, nonfunctional name. It should have been > obvious at the time clojure-mode was originally authored that the name > would have been adopted for a builtin mode if there were going to be one. >From what I know, the original author is no longer actively involved in maintaining clojure-mode, so it's hard to speculate about what their intentions were. But that is beside the point. I'm not talking about the maintainers of clojure-mode or their intentions, I'm talking about the users of clojure-mode, and how taking over the name clojure-mode would affect them after 15 years of use. -- Danny Freeman