From: "Marvin M. Doyley" <mdoyley@ur.rochester.edu>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Splitting large org file into smaller ones
Date: Sat, 30 May 2020 20:40:15 -0400 [thread overview]
Message-ID: <BEABB5D3-365D-437E-9554-1E828FCBAE6D@ur.rochester.edu> (raw)
In-Reply-To: <87ftbh4lcs.fsf@mbork.pl>
Hi Marcin,
I appreciate this, I will give it a go.
Thanks,
M
> On May 30, 2020, at 9:13 AM, Marcin Borkowski <mbork@mbork.pl> wrote:
>
>
> On 2020-05-30, at 11:51, Marvin M. Doyley <mdoyley@ur.rochester.edu> wrote:
>
>> Hi there,
>>
>> Is there an efficient way to split a large org file into smaller ones?
>
> I do not know about "efficient", but you might find my org-one-to-many
> library useful: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mbork_org-2Done-2Dto-2Dmany&d=DwIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=iHWQZlKMtTtC96Iqx0ymA0VpA5m6A73UehcV_vuh1tM&s=6rsipfH8vh-XeWLb1NEWAcdpcTFAfyUOLHD5Pkmea2o&e=
> (Note that I don't wven know if it works with newer versions of Org; if
> not, drop me a line, maybe I'll be able to fix it.)
>
> Best,
>
> --
> Marcin Borkowski
> https://urldefense.proofpoint.com/v2/url?u=http-3A__mbork.pl&d=DwIBAg&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=T41F_5QsIVBGYhPPUkgYHUp9iPHgs2rOCjs7rfKaTMU&m=iHWQZlKMtTtC96Iqx0ymA0VpA5m6A73UehcV_vuh1tM&s=VLUzcQS7YObsdTrrwTldDMYEUZJlqE3mMIxxY8tN9JQ&e=
next prev parent reply other threads:[~2020-05-31 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 9:51 Splitting large org file into smaller ones Marvin M. Doyley
2020-05-30 13:13 ` Marcin Borkowski
2020-05-31 0:40 ` Marvin M. Doyley [this message]
2020-05-30 14:37 ` Tim Visher
2020-05-30 15:36 ` William Denton
2020-05-30 18:18 ` Julius Dittmar
2020-05-31 0:42 ` Marvin M. Doyley
2020-05-30 22:23 ` Diego Zamboni
2020-05-31 0:41 ` Marvin M. Doyley
2020-05-31 15:29 ` John Kitchin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BEABB5D3-365D-437E-9554-1E828FCBAE6D@ur.rochester.edu \
--to=mdoyley@ur.rochester.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.