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 19:53:53 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> <878rvi1d6j.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="24414"; 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 17:59:43 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 1n8PvT-0006CQ-5h for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 17:59:43 +0100 Original-Received: from localhost ([::1]:47546 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8PvS-0001eq-4y for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 11:59:42 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33660) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Ppl-0007OW-20 for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 11:53:49 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:34385) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Pph-0005eB-8E; Fri, 14 Jan 2022 11:53:48 -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.0000000061E1AA94.0000399D; Fri, 14 Jan 2022 09:53:40 -0700 Mail-Followup-To: Tassilo Horn , Davin Pearson , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <878rvi1d6j.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:135289 Archived-At: * Tassilo Horn [2022-01-14 19:43]: > I think we both agree that the missing license is the main issue, not > the Copyright notice. Those terms are related. If there is copyright notice and otherwise license missing, then it is automatically proprietary, that is how it is in most of countries. If there is however, copyright notice, but license somewhere else in the directory of the file, then that is already good. But the GNU GPL suggests (maybe requires) the notice in each file, as files may be singly distributed. Then how would the recipient know under which license it was issued if the notice is not in the file. > I don't think that an emacs package is a modification of emacs itself or > a derivative work. If you modify variable you are modifying Emacs. If you create a function than such software modifies Emacs as function did not exist in Emacs. It creates new function. Thus new function is modification of Emacs itself. You have to review the license for full understanding. > Rather the package links to emacs, i.e., emacs is a kind of > "standard library" for all emacs packages. It is not enough of the excuse. 😝 Creating a function or program, small or large, meant for Emacs Lisp means it will modify Emacs as it adds new function, thus such function shall be compatible to Emacs license. Yes, that means all of the init files, configurations and snippets should carry such notices of being compatible, otherwise they are not and are automatically proprietary. > But I'm not sure if merely posting some basically private code somewhere > on a private homepage or on some pastebin requires you to add a license > notice. It does, otherwise it is considered incompatible to Emacs as it is automatically proprietary. > I mean, hundreds share their .emacs file on the web without thinking > about licensing. That is exactly the reason why I am mentioning this all. Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/