From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Fwd: How do I go about debugging my Elisp code? Date: Fri, 14 Jan 2022 18:20:39 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="313"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.1.5+104 (cd3a5c8) (2022-01-09) Cc: Davin Pearson , help-gnu-emacs@gnu.org To: Tassilo Horn Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 14 16:24:51 2022 Return-path: Envelope-to: geh-help-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 1n8ORe-000AP4-Oh for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 16:24:50 +0100 Original-Received: from localhost ([::1]:37484 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8ORd-0008WA-BV for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 10:24:49 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:36326) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8OPt-0008Vn-NZ for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 10:23:01 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:35359) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8OPr-0006gM-IN; Fri, 14 Jan 2022 10:23:01 -0500 Original-Received: from localhost ([::ffff:41.210.145.184]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000005BED3.0000000061E1954F.00002E9D; Fri, 14 Jan 2022 08:22:54 -0700 Mail-Followup-To: Tassilo Horn , Davin Pearson , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87czku1hon.fsf@gnu.org> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135287 Archived-At: * Tassilo Horn [2022-01-14 18:06]: > Jean Louis writes: > > > * Davin Pearson [2022-01-13 04:27]: > >> http://davinpearson.nz/binaries/dmp-padderise2.el > > > > After the first review of that file, I can see "Copyright" related to > > your name. However, that makes the software proprietary. > > Nonsense. Maybe there is something you did not understand, or I have expressed myself unsufficiently. That is why you call it "nonsense". When person does not provide a license reference in any kind of software, including in Emacs configuration files (which is software), but says that it is copyrighted, in absence of the free license that software is proprietary. Do you understand it? > It is perfectly fine to have individual authors and contributors as > copyright holders. That is because I have not expressed myself sufficiently. It really does not matter who is copyright holder. What matters is that there is no compatible free software license in the software. That is what I forgot to mention. > Only if a package wants to become part of emacs (GNU ELPA), one has > to assign the copyright to the FSF. I did not refer to assigning copyrights to FSF. I have referred to how package should look like in relation to legality. Who has copyrights is there not relevant. What is relevant, and what I missed to describe enough is the absence of compatible license reference. I am assuming that author wanted to provide such reference and that his m4 macros are not finished. > But it would still be fine for NonGNU ELPA if it had a proper > license statement (which is the actual missing part). Licensing requirements are not related to ELPA or NonGNU ELPA or any repository. They are generally related to the license under which Emacs is issued, so license has to be compatible. It is not relevant how is software published. > However, that file is basically a demo for debugging by adding a printed > message after each line with no intention of becoming part of emacs, so > ¯\_(ツ)_/¯. That is incorrect. Software modifies Emacs, thus has to be compatible to same free software license under which Emacs is issues. The same is valid for all other software that is modifying Emacs. In other words, when somebody creates a function for Emacs it is software modifying Emacs and shall be under compatible software license. Like GNU GPL v3+ Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/