From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: [RFC] Moving "manual.org" into core Date: Mon, 22 Jan 2018 17:00:45 +0000 Message-ID: References: <87bmhooaj9.fsf@nicolasgoaziou.fr> <87tvveqi7u.fsf@bzg.fr> <87wp0a57i5.fsf@nicolasgoaziou.fr> <87lggp6fvh.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11493148a141aa0563605fcd" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38367) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edfT1-0001gm-Mq for emacs-orgmode@gnu.org; Mon, 22 Jan 2018 12:01:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edfSx-0005Xr-If for emacs-orgmode@gnu.org; Mon, 22 Jan 2018 12:01:07 -0500 In-Reply-To: <87lggp6fvh.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: Bastien Guerry , Achim Gratz , Org Mode List --001a11493148a141aa0563605fcd Content-Type: text/plain; charset="UTF-8" On Mon, Jan 22, 2018 at 11:02 AM Nicolas Goaziou wrote: > "manual.org" is not meant to be exported to HTML through "ox-html", but > using Texinfo itself. AFAIK, Texinfo does not highlight specially Org > syntax, so using "begin_src org" is not very important for export. > I am hoping that using "begin_src org" preserves the meta data that a code block is an Org snippet when the Org manual HTML pages are published on orgmode.org. Moreover, the advantage of using "begin_example" instead is: > 1. we can use fixed-width for one-liners, > I personally don't see that as a big advantage. Whether the snippet is a single line or more, one can just select those and use the Org structural template insertion to wrap that with "#+begin_src org" .. "#+end_src". > 2. Org fontification for source blocks can be sometimes misleading, > as you sometimes cannot what is an example and what is not. > I didn't understand that limitation. I use Org src blocks quite liberally in this Org document[1], some even with nested non-Org src blocks. #+BEGIN_SRC org :noweb-ref src-block-n-default-continue ,#+BEGIN_SRC emacs-lisp +n ;; This will be listed as line 22 (message "This is line 23") ,#+END_SRC #+END_SRC I haven't found any issue. While pasting that example, I realized, that you don't even need to specially made an Org snippet an src block just because you want to use it as a noweb ref in the manual. Making Org snippets, src blocks, always, just feels like the right thing. [1]: https://raw.githubusercontent.com/kaushalmodi/ox-hugo/master/test/site/content-org/all-posts.org -- Kaushal Modi --001a11493148a141aa0563605fcd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jan 22= , 2018 at 11:02 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
"ma= nual.org" is not meant to be exported to HTML through "ox-htm= l", but
using Texinfo itself. AFAIK, Texinfo does not highlight specially Org
syntax, so using "begin_src org" is not very important for export= .

I am hoping that using "begin_sr= c org" preserves the meta data that a code block is an Org snippet whe= n the Org manual HTML pages are published on orgmode.org.

Moreover, the advantage of using "begin_example" instead is:
1. we can use fixed-width for one-liners,

I personally don't see that as a big advantage. Whether the snippet = is a single line or more, one can just select those and use the Org structu= ral template insertion to wrap that with "#+begin_src org" .. &qu= ot;#+end_src".
=C2=A0
https://raw.githubusercont= ent.com/kaushalmodi/ox-hugo/master/test/site/content-org/all-posts.org<= br>


--

Kaushal= Modi

--001a11493148a141aa0563605fcd--