From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "Why is emacs so square?" Date: Fri, 24 Apr 2020 15:09:26 +0300 Message-ID: <83wo659jbd.fsf@gnu.org> References: <863691n4xl.wl-me@enzu.ru> <86blno9yle.wl-me@enzu.ru> <87d0845msg.fsf@yahoo.com> <87h7xgjasw.fsf@yahoo.com> <875zdwjais.fsf@yahoo.com> <6a198677-41b6-4dbd-39d0-2b01550d53cf@yandex.ru> <32f6a2ce-e30f-059f-dcd4-233d666a10a1@yandex.ru> <87r1whiape.fsf@fastmail.fm> <87blnjopd0.fsf@nicolasgoaziou.fr> <83v9lregx0.fsf@gnu.org> <83v9lqclfi.fsf@gnu.org> <83h7x9b3p3.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="79360"; mail-complaints-to="usenet@ciao.gmane.io" Cc: joostkremers@fastmail.fm, rms@gnu.org, mail@nicolasgoaziou.fr, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 24 14:10:22 2020 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 1jRx9y-000KYB-4j for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Apr 2020 14:10:22 +0200 Original-Received: from localhost ([::1]:33624 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRx9x-0005SR-5C for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Apr 2020 08:10:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36118) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRx9R-0004lh-2S for emacs-devel@gnu.org; Fri, 24 Apr 2020 08:09:49 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52107) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRx9P-0003xh-ND; Fri, 24 Apr 2020 08:09:47 -0400 Original-Received: from [176.228.60.248] (port=3765 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jRx9G-0001Jw-9n; Fri, 24 Apr 2020 08:09:39 -0400 In-Reply-To: (message from Robert Pluim on Fri, 24 Apr 2020 13:34:13 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:247694 Archived-At: > From: Robert Pluim > Cc: rms@gnu.org, joostkremers@fastmail.fm, mail@nicolasgoaziou.fr, > emacs-devel@gnu.org > Date: Fri, 24 Apr 2020 13:34:13 +0200 > > Eli> I think we should try changing the documentation first, as that is a > Eli> Good Thing anyway. When that is done, we could consider whether any > Eli> code changes are needed. (I actually expect that to become evident > Eli> while the documentation is re-written in the directions I proposed: > Eli> whoever will do that job will discover that, for example, to be able > Eli> to produce a stand-alone document with Org, one would need features > Eli> that currently belong to some unrelated Org part -- which would mean > Eli> some code needs to be added or modified to make that feature > Eli> seamlessly available to document-writers.) > > That depends on what you mean by 'stand-alone'. The built-in Org mode > from 'emacs -Q' can export to at least html, latex, pdf and odt by > default, of which only latex and pdf require the installation of extra > external tools. That's orthogonal. By "stand-alone" I meant a document that doesn't require support from any additional Org features, like TODO notes, calendar appointments, etc. Just a document that includes structured text.