From mboxrd@z Thu Jan 1 00:00:00 1970 From: flammable project Subject: Re: How to automatic list org files via Elisp and then, import them for an HTML export Date: Mon, 29 Oct 2012 09:34:22 +0100 Message-ID: References: <87bofombfr.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b5d93a549721604cd2e891c Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSknl-000523-HI for emacs-orgmode@gnu.org; Mon, 29 Oct 2012 04:34:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TSknf-0007hC-Bc for emacs-orgmode@gnu.org; Mon, 29 Oct 2012 04:34:29 -0400 Received: from mail-vc0-f169.google.com ([209.85.220.169]:48183) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSknf-0007h6-5t for emacs-orgmode@gnu.org; Mon, 29 Oct 2012 04:34:23 -0400 Received: by mail-vc0-f169.google.com with SMTP id fl17so5653274vcb.0 for ; Mon, 29 Oct 2012 01:34:22 -0700 (PDT) In-Reply-To: <87bofombfr.fsf@bzg.ath.cx> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Cc: emacs-orgmode@gnu.org --047d7b5d93a549721604cd2e891c Content-Type: text/plain; charset=ISO-8859-1 Ho! I was thinking that giving the more details will eliminated doubts and misunderstanding. So to be clear enough, there was two questions in my previous message: 1/ In E-LISP, how to parse a directory containing Org files and import them with the "#+INCLUDE" function? I used those two functions. They parsed the directory and listed the org files. But my lake of skills in elisp programming is obvious! #+BEGIN_SRC emacs-lisp :exports results (let ((default-directory "~/path/to/the/directory/posts/")) (file-expand-wildcards "?org")) #+END_SRC #+BEGIN_SRC emacs-lisp :exports results (directory-files "~/path/to/the/directory/posts/" nil "\\.org\\'") #+END_SRC 2/ When I use "#+INCLUDE" for org files, the exporter mixed the hierarchy in the HTML generated. Each time I used ":minlevel 1" as argument but the exporter seem to create a sub-level of hierarchy, which doesn't represent the true hierarchy in the imported org files? Is it a bug? I hope it's minimal enough now! Thanks Bastien for Org Mode and helps! Basile 2012/10/27 Bastien > Hi Flammable (!), > > flammable project writes: > > > If someone can help me to do this I will really appreciate! > > I think we will be able to help with a more limited example. > Keep it minimal, if possible... > > Thanks in advance, > > -- > Bastien > --047d7b5d93a549721604cd2e891c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ho!=A0

I was thinking that giving the more details will = eliminated doubts and misunderstanding.

So to be c= lear enough, there was two questions in my previous message:

1/ In E-LISP, how to parse a directory containing Org files and = import them with the "#+INCLUDE" function?
I used those two functi= ons. They parsed the directory and listed the org files. But my lake of ski= lls in elisp programming is obvious!
#+BEGIN_SRC emacs-lisp :exports results
(let ((default-directory "~/path= /to/the/directory/posts/"))
=A0 =A0 (file-expand-wildcards "= ?org"))
<= font face=3D"courier new, monospace">#+END_SRC

#+BEGIN_SRC emacs-lisp :exports resul= ts
(directory-files "~/path/to/the/directory/posts/"
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0nil =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&q= uot;\\.org\\'")
#+END_SRC


2/ When I use "#= +INCLUDE" for org files, the exporter mixed the hierarchy in the HTML = generated. Each time I used ":minlevel 1" as argument but the exp= orter seem to create a sub-level of hierarchy, which doesn't represent = the true hierarchy in the imported org files? Is it a bug?

I hope it's minimal enough now! Thanks Bastien for = Org Mode and helps!

Basile







2012/10/27 Bastien <bzg@altern.org>
Hi Flammable (!),

flammable project <flamma= ble.project@gmail.com> writes:

> If someone can help me to do this I will really appreciate!

I think we will be able to help with a more limited example.
Keep it minimal, if possible...

Thanks in advance,

--
=A0Bastien

--047d7b5d93a549721604cd2e891c--