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 18:24:22 +0100 Message-ID: <87ilumus54.fsf@gnu.org> References: <87czku1hon.fsf@gnu.org> <878rvi1d6j.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28774"; 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 18:48: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 1n8QgS-0007It-QB for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 18:48:17 +0100 Original-Received: from localhost ([::1]:50802 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8QgR-0002qu-5V for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 12:48:15 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44052) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Qf6-0002qU-Qq for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 12:46:52 -0500 Original-Received: from [2001:470:142:3::e] (port=47204 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 1n8Qf6-0005A4-2b; Fri, 14 Jan 2022 12:46:52 -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=eVFCZV+Vd1zyOy1RgjYV9Wxoevguh3TYx3qownO8RHo=; b=eyrXLzMLYQE/2N +70qdRelX3fQjNMvFtR1+H+HQUQRsUBhGcIn8465uVWacYx0gSpa96k1xHqi/vFYzGTBZ9L0sOo/K xErMe0pUvCZFfZM1eBmUBlcmgMiVgaOBvhFsHsfz5TQtyIZs4BD6DUa6rEjkQrnWUa35UIJFmois4 bvFM2gb4r24pJ6kh64zB6g1hSUjiZpGphePDSqyEbaneOUqa6hkAn87ij5kZ9VA+TaMmzrnRj+uTW e7OL2eotoZmnXO6uOK4cf2pgCTM1qtjKUHwyvg142l3cFhCgWxmAgyQ2ZX+JVys5vCtqF/tCDFnzz s4vZPakyBuqZqMSVo8bQ==; Original-Received: from auth1-smtp.messagingengine.com ([66.111.4.227]:47467) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n8Qf6-0001q9-An; Fri, 14 Jan 2022 12:46:52 -0500 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id 41CD327C0054; Fri, 14 Jan 2022 12:46:50 -0500 (EST) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 14 Jan 2022 12:46:50 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdehgddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfhgfhffvufffjgfkgggtsehttdertddtredtnecuhfhrohhmpefvrghsshhi lhhoucfjohhrnhcuoehtshguhhesghhnuhdrohhrgheqnecuggftrfgrthhtvghrnhepue eijedtudffgfetkeelueetuedvfedvheeitddugffhuddutedvffdvgfehvefgnecuffho mhgrihhnpehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepthhhohhrnhdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihht hidqkeeijeefkeejkeegqdeifeehvdelkedqthhsughhpeepghhnuhdrohhrghesfhgrsh htmhgrihhlrdhfmh X-ME-Proxy: Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jan 2022 12:46:49 -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:135291 Archived-At: Jean Louis writes: >> 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. So if I want to give some help-searching user the hint to reproduce an error with debug-on-error set to t, I should write my reply as given in the below? --8<---------------cut here---------------start------------->8--- Could you please try using the following added to your .emacs? ;; This file is part of GNU Emacs. ;; GNU Emacs is free software: you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation, either version 3 of the License, or ;; (at your option) any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs. If not, see . (setq debug-on-error t) --8<---------------cut here---------------end--------------->8--- I mean, according to your reasoning, I'm publishing a modification of emacs here. > 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. IMHO, modification is usually meant as copying and adapting code. Setting a variable is more or less configuration. An interesting aspect are advices which allow modifying existing functions without physically touching their source code. >> 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. Well, I'd say that's kind of a grey area. Of course, elisp code that is published on the interwebs without specifying a compatible license cannot be subject for inclusion or linkage in my super-duper elisp package which I intend to publish on some package archive. However, I wouldn't go so far to accuse someone posting his ~/.emacs or some other code snippets of license infringement. Bye, Tassilo