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 22:02:36 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> <878rvi1d6j.fsf@gnu.org> <87wnj2f8oi.fsf@mbork.pl> 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="6703"; 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, Tassilo Horn To: Marcin Borkowski Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 14 20:04:23 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 1n8Rs7-0001Yi-Jx for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 20:04:23 +0100 Original-Received: from localhost ([::1]:59486 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8Rs6-0005ey-MT for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 14:04:22 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33440) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Rqn-0005do-7h for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 14:03:01 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:38339) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Rql-0008QS-Bu; Fri, 14 Jan 2022 14:03:00 -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 0000000000037E5B.0000000061E1C8E0.00004266; Fri, 14 Jan 2022 12:02:55 -0700 Mail-Followup-To: Marcin Borkowski , Tassilo Horn , Davin Pearson , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87wnj2f8oi.fsf@mbork.pl> 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:135295 Archived-At: * Marcin Borkowski [2022-01-14 21:56]: > > On 2022-01-14, at 17:53, Jean Louis wrote: > > > 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. > > If this were true, wouldn't it imply that most of > emacs.stackexchange.com is copyright infringement? That code published on Emacs StackExchange is compatible to Emacs. As you have referenced it below, code published on Stack Exchange is under Creative Commons BY-SA 4.0., so your reference is here: https://www.gnu.org/licenses/license-list.html#ccbysa This is a copyleft free license that is good for artistic and entertainment works, and educational works. Like all CC licenses, it should not be used on software. CC BY-SA 4.0 is one-way compatible with the GNU GPL version 3: this means you may license your modified versions of CC BY-SA 4.0 materials under GNU GPL version 3, but you may not relicense GPL 3 licensed works under CC BY-SA 4.0. Because Creative Commons lists only version 3 of the GNU GPL on its compatible licenses list, it means that you can not license your adapted CC BY-SA works under the terms of “GNU GPL version 3, or (at your option) any later version.” However, Section 14 of the GNU GPL version 3 allows licensors to specify a proxy to determine whether future versions of the GNU GPL can be used. Therefore, if someone adapts a CC BY-SA 4.0 work and incorporates it into a GNU GPL version 3 licensed project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GNU GPL is a compatible license, the adapted and combined work could be used under that later version of the GNU GPL. > --8<---------------cut here---------------start------------->8--- > Subscriber Content > > You agree that any and all content, including without limitation any and > all text, graphics, logos, tools, photographs, images, illustrations, > software or source code, audio and video, animations, and product > feedback (collectively, “Content”) that you provide to the public > Network (collectively, “Subscriber Content”), is perpetually and > irrevocably licensed to Stack Overflow on a worldwide, royalty-free, > non-exclusive basis pursuant to Creative Commons licensing terms (CC > BY-SA 4.0), and you grant Stack Overflow the perpetual and irrevocable > right and license to access, use, process, copy, distribute, export, > display and to commercially exploit such Subscriber Content, [...] > --8<---------------cut here---------------end--------------->8--- > > (from https://stackoverflow.com/legal/terms-of-service#licensing) -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/