From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.help Subject: Re: Fwd: How do I go about debugging my Elisp code? Date: Fri, 14 Jan 2022 17:23:41 +0100 Message-ID: <878rvi1d6j.fsf@gnu.org> References: <87czku1hon.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40232"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.5; emacs 29.0.50 Cc: Davin Pearson , help-gnu-emacs@gnu.org To: Jean Louis Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 14 17:47:17 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 1n8PjR-000AGU-1C for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 17:47:17 +0100 Original-Received: from localhost ([::1]:37084 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8PjQ-0001ol-5L for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 11:47:16 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58594) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Pf7-00088l-3T for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 11:42:49 -0500 Original-Received: from [2001:470:142:3::e] (port=45572 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Pf6-0003qo-DE; Fri, 14 Jan 2022 11:42:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-reply-to:Date:Subject:To:From: References; bh=O7dbzRmdTgKSIwisCvqgNXrxjcpfSFIq3ddJ/gMguos=; b=TaSOLVNAKBJcY9 LYc73bk37xTRKilXXQw7AG9X1mYlpKDXza23OwrTY+7nd/irKPsQ2gYfn5N0IiE8FcGkq97sL8QSl z2mKIs10GgEbrcZ8cMmkwUwt/lpi+vzkYRM7q8rWwiiziB+qSQZeEIkDdhVirHkiAUXNEZGg7a07g PeWDIepOp+fSjDdbNmIXF/BB+kT97pxAiLE870pgFiDEqG88DwkHfI1fPy634E+rImzBcGxC+v9MS 6tJOHIdq04bNJuR5oEj4WRaSf2vyDlvlmo2IeUaJF7SsrmCNyW2155eTcxgbO8xT4th6b0E0c9jEt 8DUWzyah9wdfeh3ILi9g==; Original-Received: from auth2-smtp.messagingengine.com ([66.111.4.228]:52953) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n8Pf6-0007tP-PQ; Fri, 14 Jan 2022 11:42:48 -0500 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id B6DAE27C0054; Fri, 14 Jan 2022 11:42:46 -0500 (EST) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 14 Jan 2022 11:42:46 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdehgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpehffgfhvffuffgjkfggtgfgsehtqhertddtreejnecuhfhrohhmpefvrghsshhi lhhoucfjohhrnhcuoehtshguhhesghhnuhdrohhrgheqnecuggftrfgrthhtvghrnhepie dugffhhfejveevvdfhffegteelleejffefgefgueeggeelheefieeujefhheegnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhrnhdomh gvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqkeeijeefkeejkeegqdeifeehvdel kedqthhsughhpeepghhnuhdrohhrghesfhgrshhtmhgrihhlrdhfmh X-ME-Proxy: Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jan 2022 11:42:45 -0500 (EST) In-reply-to: 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:135288 Archived-At: Jean Louis writes: Hi Jean, I think we both agree that the missing license is the main issue, not the Copyright notice. >> 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 =C2=AF\_(=E3=83=84)_/=C2=AF. > > 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+ I don't think that an emacs package is a modification of emacs itself or a derivative work. Rather the package links to emacs, i.e., emacs is a kind of "standard library" for all emacs packages. But even then, it needs to have a license compatible with emacs' license, yes. 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. I mean, hundreds share their .emacs file on the web without thinking about licensing. Bye, Tassilo