From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs (was: Convert README.org to plain text README while installing package) Date: Sat, 11 Jun 2022 20:42:27 -0400 Message-ID: References: <87h74ztshe.fsf@gmx.de> <871qw31ois.fsf@yahoo.com> <8735gj4ceo.fsf@gnu.org> <87ee038ipt.fsf@gmx.de> <87o7z61v59.fsf@gmail.com> <87bkv527p5.fsf@gmail.com> <835yld93w7.fsf@gnu.org> <877d5t0yrn.fsf@gmail.com> <87r140yuof.fsf@gmail.com> <875yl9e7zm.fsf@gmail.com> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19128"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 02:43:26 2022 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 1o0BhN-0004lQ-Aq for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 02:43:25 +0200 Original-Received: from localhost ([::1]:56822 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0BhL-0005Gx-QO for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jun 2022 20:43:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0BgT-0004AX-VM for emacs-devel@gnu.org; Sat, 11 Jun 2022 20:42:29 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36714) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0BgS-00073o-Co; Sat, 11 Jun 2022 20:42:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=5AiRfcWB7pEGq6LWKTSQS7ARGj3NsRCeo0LyWJeAqgw=; b=oW9FSDO7ClXn ryBW9oIx87aNnK+1S+1LvCD1rn20SCdeguuwu/N1TiIFbyO1YVzbgBfHUVTz3dqVxKfQo0A//flXg kksLl0Uqee8j/oNmUMV5zvXt/7sTn4LQUHKdzTOSU2q7h0UIZk5aVf0ghsf2NdIYuhGufC06Vgcol 2SodJcEj9rFLjIkI1OFt61eEtgY3dWm0FRd3V2ifOHfPQybYrJmnmnJi55KYReuVEmJFSa52WMHGa 0ww9Mm8Ahj4f2lXZVfSVUmSyoKg3k5zZpq3zE1YNxHwY7ibCMIKxIFITf3o7wqgEH2balypO8ddkO AXi6oIhG3sB/U7sYm8b08Q==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1o0BgR-0008J7-Ts; Sat, 11 Jun 2022 20:42:27 -0400 In-Reply-To: <875yl9e7zm.fsf@gmail.com> (message from Tim Cross on Fri, 10 Jun 2022 09:10:50 +1000) 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" Xref: news.gmane.io gmane.emacs.devel:291048 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Making org mode syntax equivalent to texinfo syntax seems like a > mistake to me. If this succeeds, it would be an important advance for the GNU system. We would replace Texinfo with a much cleaner system, easier to use and more maintainable. Not solely for Emacs, but for ALL our documentation! The original idea was to have a light weight syntax which > is easyh to learn, not create a clone of texinfo. Besides, I suspect it > would be very difficult to maintain backwards compatibility. These are real concerns, but they are not real certainties. If we look for solutions, we may find good ones. I hope someone will give it a try. One of Texinfo's crucial features is a wide range of semantic markup constructs, each of which can generate different output depending on the output format. For instance, Texinfo has @var, @emph and @dfn, all of which generate italics in printed output, but they differ in what they generate for other output formats. There are probably 15 other such constructs. These constructs make it possible to carry out our documentation style constructs. Does Org format have the ability to make all these distinctions? If not, I suspect that the Org mode documentation isn't following all our style conventions for documentation. There is nothing fundamentally hard about supporting these distinctions. Can someone please examine which ones Org supports and which ones not, and propose exensions for the ones not yet supported? -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)