From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs Date: Sat, 02 Sep 2023 08:19:02 +0000 Message-ID: <87jzt9gf7t.fsf@localhost> References: <83msyemjx8.fsf@gnu.org> <871qfpoij6.fsf@gnu.org> <87fs45ivyo.fsf@localhost> <874jkh54qu.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28881"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Bastien Guerry , jemarch@gnu.org, eliz@gnu.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 02 10:19:33 2023 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 1qcLqu-0007G0-6e for ged-emacs-devel@m.gmane-mx.org; Sat, 02 Sep 2023 10:19:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcLq5-0003x7-6w; Sat, 02 Sep 2023 04:18:41 -0400 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 1qcLq3-0003wr-0n for emacs-devel@gnu.org; Sat, 02 Sep 2023 04:18:39 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qcLpo-0000ng-Cs for emacs-devel@gnu.org; Sat, 02 Sep 2023 04:18:38 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DAFED240103 for ; Sat, 2 Sep 2023 10:18:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693642701; bh=0HtW3LWDmBh6Y4DK7AZY0rHvxuujB0D+ldz7MfsGkpM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=G9N4ZxWUpmxLyhLqWDX/cWiXjgar+3UasjhWV+TIZgjK5kDQmN1hmcHyMmpkJHXD4 wIeAsk35mrVC7G2optb+AZnmW2w8lET6AFDPgElrUYoXL803K0FoSySf2++A58Pbof zappdOHtUMtjtU5UbxHNVfYlfibq92xKBw4DJdAXe0FNzISDQuGmnEhCbCuamWSpzn NWxKe5hC//PcH+F6645/2t9A5jU8hi6ikBZRKH3/zaoy+t+ygFrSlP+v+phHOCIVyA ZlVYchPDTAxX45nbaUfYLoWBzP4rFIxFCB5BbWbJJjaZb/PsBs8fIjVeC19OWeIOtd c5YxGcKTIHIzg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Rd77x1WJxz6tmv; Sat, 2 Sep 2023 10:18:21 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action 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:309856 Archived-At: Richard Stallman writes: > > The .org falls in the category of lightweight markup formats and I > > believe it should stick close to this definition. > > If people keep this unchanged, Org mode will remain useful for the > tasks it can do today. But it won't be able to do the job for which > we now use Texinfo. > There are many different Texinfo markup constructs, so to do the job > of Texinfo, Org mode would need to be able to distinguish them all. > > So the basic question is: to extend Org mode to do that job, or not? I don't think that we need to compromise here. We can keep Org lightweight yet allowing arbitrary markup. We already have arbitrary environment markup (special blocks): #+begin_ ... #+end_ like #+begin_center #+begin_abstract #+begin_myweirdlatexenvironment etc These are all valid Org markups, but only a small subset of them has special handling by Org. Other free-form special blocks are simply ignored (or handled generically), for example, on export, unless the specific export backend implements special handling for a given block type. Supporting TeXinfo-specific inline markup can be done using the same approach, without complicating core Org markup specifications. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at