From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: SachaC-news Date: Mon, 01 Jan 2024 14:01:39 +0200 Message-ID: <83v88d1cv0.fsf@gnu.org> References: <83zfxq182m.fsf@gnu.org> <3a6ed189-a56f-4249-9616-047724bc979a@alphapapa.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15252"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, cnngimenez@disroot.org, emacs-devel@gnu.org To: Adam Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 01 13:02:36 2024 Return-path: Envelope-to: ged-emacs-devel@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 1rKH07-0003jF-VM for ged-emacs-devel@m.gmane-mx.org; Mon, 01 Jan 2024 13:02:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rKGzR-00055G-B3; Mon, 01 Jan 2024 07:01:53 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rKGzP-00054x-DB for emacs-devel@gnu.org; Mon, 01 Jan 2024 07:01:51 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rKGzO-0000jZ-T2; Mon, 01 Jan 2024 07:01:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=87+jT4XXWaORcwaG+o6/06uzl71A2NT0QD5EkOO1u9g=; b=EB8uZo4YWB91 ZrqDUstm4zTnAN3TNri6Sda26A0MuaBRanHolA0N/UHgwAPZ2uLLupYyWJav4O7H3NotnDKjlJKVM fJqZS8pafWdnIxVqBcvfeiKqR9U+30BVyDAOb5kZnQTjxtFkJJZRAJSVoKwOUaJUC3hMgPden/AUL SiI9WOwfTvN9Oan8kXvs0Yw1WI0bH0hddMboeGAJw8uBxSQvDJYr+Vsjtvur+cP3GGOeqmSEPNbr5 ibsLt7V7oz9rCHZOqiTzb+u0/1nWNHv1A/eoIG1a4Rfo3itf+Cr6+PAJCFXQSTGKkwCxlKt9T+fnm ky+xA/cqQbxDhB6jqZTUOw==; In-Reply-To: <3a6ed189-a56f-4249-9616-047724bc979a@alphapapa.net> (message from Adam Porter on Sun, 31 Dec 2023 15:36:40 -0600) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314414 Archived-At: > Date: Sun, 31 Dec 2023 15:36:40 -0600 > Cc: rms@gnu.org, cnngimenez@disroot.org, emacs-devel@gnu.org > From: Adam Porter > > On 12/31/23 13:32, Eli Zaretskii wrote: > >> Date: Sun, 31 Dec 2023 12:13:24 -0600 > >> Cc: cnngimenez@disroot.org, emacs-devel@gnu.org > >> From: Adam Porter > >> > >>> Org format is text with its own kind of markup -- it is not plain text. > >> > >> Many users would disagree. > > > > How can users disagree with something that is a plain fact? > > A fact? Org's own web site, as I said, proclaims, "Your life in plain > text." It would seem there is at least room for interpretation. If there's room for interpretation, why do you object to Richard's (and mine)? > > Do you deny that Org files have their own specialized markup? Because > > that's all that Richard said above. If you do agree that Org has its > > own markup, then where are you going with your objections and > > arguments? > > He said that the package in question should have the output of one of > its commands changed to not output Org syntax. With Org being > "essentially" plain text, and intended to be readable as plain-text in > any software, without any special fontification, that raises the > question of what would be changed to qualify the command's output as > non-Org "plain text", and what the benefit would be to the user. I think you are splitting hair, because it's crystal clear what Richard asked for: produce output without Org's markup. Saying that the request is already satisfied based on the differences in interpreting what is and isn't "plain text' is not useful here, since, given the reference to Org markup, it should be clear what Richard meant when he said "plain text" in this case.