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: Sat, 15 Jan 2022 10:34:11 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> <878rvi1d6j.fsf@gnu.org> <87ilumus54.fsf@gnu.org> <87ee5aw12x.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1491"; 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 Sat Jan 15 08:43:03 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 1n8diI-0000Al-Td for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 15 Jan 2022 08:43:02 +0100 Original-Received: from localhost ([::1]:44322 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8diH-0007qD-JE for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 15 Jan 2022 02:43:01 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59644) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8ddS-0007pX-NF for help-gnu-emacs@gnu.org; Sat, 15 Jan 2022 02:38:03 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:48119) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8ddQ-0004LR-5z; Sat, 15 Jan 2022 02:38:02 -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.0000000061E279D5.00006735; Sat, 15 Jan 2022 00:37:57 -0700 Mail-Followup-To: Tassilo Horn , Davin Pearson , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87ee5aw12x.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:135315 Archived-At: * Tassilo Horn [2022-01-14 22:48]: > Jean Louis writes: > > >> 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? > > > > I would assume that your minimal contributions to Emacs are under the > > same license as Emacs and simply include it how it is in my code if I > > wish, but then I would say it was authored by yourself. Then in case > > of complaint from your side I could adapt it how you and me think it > > is alright. > > > > It is good to be practical. > > I guess with elisp, it will never ever happen that the author of some > code in some posting will complain. But noting down the author along > the code is a very good idea because of copyright, i.e., when you later > want to contribute your package to emacs or publish it on GNU ELPA. Look at plethora of Emacs packages on various repositories, large majority of them are properly licensed. This is because of policies established at repository and their quick verification. Few are improper or not adequate. Those packages beyond repositories often lack licenses. They need practical reminder. Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/