From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Jose E. Marchesi" Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs Date: Sat, 26 Aug 2023 18:49:49 +0200 Message-ID: <871qfpoij6.fsf@gnu.org> References: <83msyemjx8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3665"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: rms@gnu.org, bzg@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 26 18:50:48 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 1qZwUq-0000p2-GJ for ged-emacs-devel@m.gmane-mx.org; Sat, 26 Aug 2023 18:50:48 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZwUL-0003yX-Nu; Sat, 26 Aug 2023 12:50:17 -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 1qZwUK-0003yL-8v for emacs-devel@gnu.org; Sat, 26 Aug 2023 12:50:16 -0400 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 1qZwUJ-000095-S6 for emacs-devel@gnu.org; Sat, 26 Aug 2023 12:50:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=cYYUuR+Wqdo+TWyzRVmLexhNkh/51ByazICopL2UMmM=; b=PFNS8ZONcq6q4if4cINn cBQ53r0hyd+We7MDRr8Oixf6G6iV4R+lixOIFa7jEUKNRoLwL2ETwF1sLLmIYNPuU3vvNzaxMHZ8e JZqUeUETBN/JWI/ElLzVOqkTxnKtKhg9MciLnhjLI2wNPbP2UWY2ZJ/CR2hE5jlzbrho/k4i6otBN gn5CSZtf8aBt6VHczuZkpQusSl9fjhJX1/hzpNi7D6umME0/HtPyu3HxuQCeEpripdj9LTyic5bDE ImejTtQED5hKs3onTGI90d+ZKOPEdB/KPMeCCklCxkTDRNZfdQDslBo4v7T8dYeu5DuY22ajgXUxP ScasVRxK2BGvtw==; In-Reply-To: <83msyemjx8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Aug 2023 08:50:27 +0300") 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:309261 Archived-At: >> From: Richard Stallman >> Cc: emacs-devel@gnu.org >> Date: Fri, 25 Aug 2023 22:04:13 -0400 >> >> Please look at the list I sent yesterday. (See below.) Can Org mode >> handle each of them, and generate from it the correct output for each >> output format? >> >> > @code >> > @samo >> > @emph >> > @dfn >> > @var >> > @i >> > @url >> > @key >> > @kbd > > I think it can, but a typical Texinfo manual these days uses many more > commands, not just those. So this list is insufficient to judge these > issues. The actual list is much longer. I think the point here is not just these particular marks, or some other particular set. It is that "markdown-style" formats, like org-mode, are not very good supporting "inline" marking. For inline marks, Texinfo uses a conventient generic and extensible form: @NAME{CONTENT}. "markdown-style" formats, on the contrary, generally support a closed set of marks that use delimited based ad-hoc syntax, such as *foo*, =foo=, "foo", `foo' and so on. Block marks are usually supported well enough by these formats. In the case of org it would be #+BEGIN_WHATEVER end #+END_WHATEVER I suppose.