From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Brand new clojure support in Emacs ;-) Date: Sun, 03 Sep 2023 20:02:20 +0300 Message-ID: <838r9n6vhf.fsf@gnu.org> 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> <87fs3x6ge7.fsf@gmail.com> <87v8cthmzl.fsf@dfreeman.email> <838r9pby47.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33057"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, danny@dfreeman.email, joaotavora@gmail.com, dmitry@gutov.dev, rms@gnu.org, emacs-devel@gnu.org To: Lynn Winebarger Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 03 19:03:45 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 1qcqVk-0008M6-Rc for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Sep 2023 19:03:44 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcqUr-0001bD-Oe; Sun, 03 Sep 2023 13:02:49 -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 1qcqUp-0001aq-GN for emacs-devel@gnu.org; Sun, 03 Sep 2023 13:02:47 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qcqUo-0006Z9-Tt; Sun, 03 Sep 2023 13:02:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=mRXCQXjZFAMIS/d1lwRhd+ubpmk6X25Wvz01K9qWv8g=; b=N8I84AMLlXVj NklXqO3lnIkkp72LaWdgnq+SHnxX3y2CNIoYvWjX3P7fvLmBSSIfxyKCjUalUSl064kDou7KJHLFI vyg+g78Ei3rrhf/S0/F6JTCBRoCUOZ0br2kOhUBn6bDxZkP90LKe4MLEU8gqoDrmsWne+xqkORQ9Q MqG4e4PEX6byQ+qNBu5vjIzIbPtQeuxBNqbyZBkxIVwXVQff2I/LZMwkziPAbC5dFHE3HnvaRNqSw MH6hz892SeHgm1PkYi1BznGU1gGUUCXsCXsBOlUANueV0y2rKVfu1EWsCamEiYIyVwTGLghAc32Fp oh+4IXQx5BIVnmk4jUpKCA==; In-Reply-To: (message from Lynn Winebarger on Sun, 3 Sep 2023 12:53:11 -0400) 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:310008 Archived-At: > From: Lynn Winebarger > Date: Sun, 3 Sep 2023 12:53:11 -0400 > Cc: Yuan Fu , danny@dfreeman.email, joaotavora@gmail.com, > dmitry@gutov.dev, rms@gnu.org, emacs-devel@gnu.org > > > No one who speaks for the project suggested anything like that. It's > > a non-issue. > > > So, does RMS not speak for the project? Sometimes he does, sometimes he doesn't. Like all of us: sometimes we just express a non-obligatory opinions, sometimes we describe a decision made for the project as a whole. There's no one answer; you need to read the fine print. > Am I misreading his message: > https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg01063.html ? If you think he was saying we will necessarily call our mode clojure-mode, then yes, I believe you are misreading it. From where I stand, Richard was describing a way to avoid a name conflict. In any case, whatever decision is made (and we didn't yet decide to have our own mode for Clojure), it will have to be agreed upon by Stefan and myself. > It would be better if there were some policy statement in the emacs or > elisp manual regarding library and package naming practices, though. Taking into consideration how seriously our recommendations for package names are followed (yeah, right), I very much doubt that we should spend time and energy on formulating policy that no one will follow. We have much more serious and useful tasks to accomplish, where we have a much better control on the outcome.