From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: Announcement: org-one-to-many
Date: Thu, 23 Oct 2014 19:58:48 +0200 [thread overview]
Message-ID: <87fvee652f.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <CAJKAhPCjPKL9ELFD-X4uaWyiM77sWr7Tm8fS+jRvek5+m7zDrQ@mail.gmail.com>
On 2014-10-23, at 16:39, Daniel Clemente wrote:
> Hi,
> breaking a big .org file in many small pieces is one of my major concerns
> with .org and one which gives me lots of problems. Thank you very much for
> having the clear objective of one-to-many.
You're welcome!
> If your goal is HTML export, you can do a function that iterates over all
> headers and exports them (see below). But then links are broken, you need
> to decide filenames, etc. Which is what your project solves.
Or I hope so – at least;-).
> org-one-to-many has a shortcoming which is present in so many "org to blog"
> systems: it expects a particular structure (in this case, all headers at
> the same level). I suggest you iterate over search results of a normal
> search:
>
> For instance, you can get all headers tagged with "tobesplit" like this:
> (org-map-entries (lambda () (line-number-at-pos)) "+tobesplit" 'agenda)
>
> One of the possible searches is "headers at level 2", so this new system
> would include the one you have.
I thought about it. I'd like to first make my code a bit cleaner and
fix one bug I know of. I think this will be fairly easy; I could split
headers with some property (a tag might not be a good idea, since tags
are inherited).
> Greetings
Thanks for your input!
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next prev parent reply other threads:[~2014-10-23 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 15:02 Announcement: org-one-to-many Marcin Borkowski
2014-10-21 16:10 ` Eric Abrahamsen
2014-10-21 16:58 ` Marcin Borkowski
2014-10-23 14:39 ` Daniel Clemente
2014-10-23 17:58 ` Marcin Borkowski [this message]
2014-10-24 4:06 ` Daniel Clemente
2015-02-12 22:33 ` Marcin Borkowski
2015-02-12 23:43 ` John Kitchin
2015-02-13 0:13 ` Marcin Borkowski
2015-02-13 0:34 ` John Kitchin
2015-02-13 8:44 ` Sebastien Vauban
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=87fvee652f.fsf@wmi.amu.edu.pl \
--to=mbork@wmi.amu.edu.pl \
--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).