emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: flammable project <flammable.project@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to automatic list org files via Elisp and then, import them for an HTML export
Date: Sat, 22 Dec 2012 19:50:54 +0100	[thread overview]
Message-ID: <87ip7tvex0.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAJzEwi_p5qPXRYkNyUP6XnHe2XSUVb2H-7+bs+=RDX8pGBLKHg@mail.gmail.com> (flammable project's message of "Mon, 29 Oct 2012 09:34:22 +0100")


flammable project <flammable.project@gmail.com> writes:

> 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?

MMhh... I've not explored this issue but I don't think including
several files dynamically is a good idea.

>     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?

There we need something more concrete to chew on -- can you give the two
source files (the one including and the one included) and explain why
the HTML is wrong?



      reply	other threads:[~2012-12-22 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 13:09 How to automatic list org files via Elisp and then, import them for an HTML export flammable project
2012-10-27 10:55 ` Bastien
2012-10-29  8:34   ` flammable project
2012-12-22 18:50     ` Bastien [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ip7tvex0.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=flammable.project@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).