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: Tue, 05 Sep 2023 11:04:36 +0000 Message-ID: <87cyywvq2j.fsf@localhost> References: <83msyemjx8.fsf@gnu.org> <871qfpoij6.fsf@gnu.org> <87fs45ivyo.fsf@localhost> <87h6okga15.fsf@localhost> <87cyz61cbp.fsf@localhost> <87v8cuqtkr.fsf@localhost> <83a01301-d0f1-4b54-af23-d2866412d694@gmx.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32127"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Juergen Fenn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 05 13:04:47 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 1qdTrT-0008AS-N2 for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Sep 2023 13:04:47 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdTqk-0007yd-7d; Tue, 05 Sep 2023 07:04:02 -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 1qdTqi-0007xv-Rv for emacs-devel@gnu.org; Tue, 05 Sep 2023 07:04:00 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qdTqe-0000nk-2r for emacs-devel@gnu.org; Tue, 05 Sep 2023 07:04:00 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 63C9A240029 for ; Tue, 5 Sep 2023 13:03:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693911828; bh=TpHRyAltwH5jMrxEZzndHSfLJJfCBXZwo+0FZl9f12U=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=j7zCBiAJQ4wZ7LGZ5X6SunvSuS+ZeOAMyTRp29j6TJwRY2xWdkvlresFfPw7opPzr JZUDKfidzAL6NT2JUcy8DEd3edE0CbEWwArCb7AMQaXoZWjVaJvPgFa5sVqhBwBNkK hstXe8dd63NIa6lFcOLITF8qU56BW+LawZ0sZ4uapdNP2MAQShO5HwKqwPB5s7ziKe 8YIrg8zC675SoavoJjNJQEDM8l050odt+8gAK9KJL0Zl7LC/S9V+yvrZJZpi0Oz2pc rSXqfDJTXOl3Nh0E6B6HG8FsrnPNXUNjxzw5UR1nxnWsMxH5kGAxmDEClyPRHglyuW RHayvWXzNMQAg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Rg2gR502lz9rxQ; Tue, 5 Sep 2023 13:03:47 +0200 (CEST) In-Reply-To: <83a01301-d0f1-4b54-af23-d2866412d694@gmx.net> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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=ham 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:310124 Archived-At: Juergen Fenn writes: > Am 04.09.23 um 03:32 Uhr schrieb Richard Stallman: >> But I think I see a disappointing difference between the two. Texinfo >> for manuals is semantic markup, but the proposed use of Org mode for >> manuals is not. With Texinfo, you specify what the manual contents >> should be, and in each format you get that contents as output. See what >> I mean? > > > This is an interesting point indeed. I wonder, too, whether we could add > semantic markup to Org? It's not exactly what lightweight markup > languages such as Markdown or Org are meant to be. But we would not > necessarily need this in core, a semantic add-on would probably be > enough. We would need an interface that allows for more or less freely > defining semantic markup to Org text. A semantic org mode. Hm. This is exactly what I have in mind. Similar idea is implemented in https://github.com/alhassy/org-special-block-extras -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at