Hello Marcin,
Marcin Borkowski wrote:
> so I've got this little library of mine, called org-one-to-many, which
> can split an Org file into pieces, modifying internal links so that they
> still point to the same place (even if now in another file).
>
> But I have a problem with it. I would like t
I think it doesn't matter where they go. I usally put them at the top,
but sometimes at the bottom, sometimes in a section I mark noexport to
keep them out of the way. It depends on whether someone should actually
read them, or if this is just an intermediate to an end.
Marcin Borkowski writes:
>
On 2015-02-13, at 00:43, John Kitchin wrote:
> I think it would be easy to copy all the file keywords. One way would
> just be searching by regexp. Another way could be similar to:
>
> http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/
>
> if you know in adva
I think it would be easy to copy all the file keywords. One way would
just be searching by regexp. Another way could be similar to:
http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/
if you know in advance what the important ones are.
Marcin Borkowski writes:
Hello everybody,
so I've got this little library of mine, called org-one-to-many, which
can split an Org file into pieces, modifying internal links so that they
still point to the same place (even if now in another file).
But I have a problem with it. I would like to export all the resulting
fil
El Thu, 23 Oct 2014 19:58:48 +0200 Marcin Borkowski va escriure:
> > 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
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 expo
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.
If your goal is HTML export, you can do a function that iterates over all
headers and exports them (se
On 2014-10-21, at 18:10, Eric Abrahamsen wrote:
> Marcin Borkowski writes:
>
>> Hi all,
>>
>> a long time ago I asked here about a way to split an Org file into a
>> bunch of smaller ones. One of the answers I got was that the tricky
>> part is maintaining internal links in a reasonable way.
>>
Marcin Borkowski writes:
> Hi all,
>
> a long time ago I asked here about a way to split an Org file into a
> bunch of smaller ones. One of the answers I got was that the tricky
> part is maintaining internal links in a reasonable way.
>
> It is probably overoptimistic on my side, but it seems t
Hi all,
a long time ago I asked here about a way to split an Org file into a
bunch of smaller ones. One of the answers I got was that the tricky
part is maintaining internal links in a reasonable way.
It is probably overoptimistic on my side, but it seems that this problem
is solved now. The co
11 matches
Mail list logo
