From: 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: Mon, 29 Oct 2012 09:34:22 +0100 [thread overview]
Message-ID: <CAJzEwi_p5qPXRYkNyUP6XnHe2XSUVb2H-7+bs+=RDX8pGBLKHg@mail.gmail.com> (raw)
In-Reply-To: <87bofombfr.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
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 <bzg@altern.org>
> Hi Flammable (!),
>
> flammable project <flammable.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,
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 4072 bytes --]
next prev parent reply other threads:[~2012-10-29 8:34 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 [this message]
2012-12-22 18:50 ` Bastien
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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='CAJzEwi_p5qPXRYkNyUP6XnHe2XSUVb2H-7+bs+=RDX8pGBLKHg@mail.gmail.com' \
--to=flammable.project@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).