From: Jambunathan K <kjambunathan@gmail.com>
To: Jay McCarthy <jay.mccarthy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Converting from OmniFocus to org-mode
Date: Sat, 06 Aug 2011 16:05:49 +0530 [thread overview]
Message-ID: <81d3gibzei.fsf@gmail.com> (raw)
In-Reply-To: <CAJYbDa=X6_9dazu3LnwCOki2+pEh4L5wW0n-=S2ryU94nP6FUA@mail.gmail.com> (Jay McCarthy's message of "Fri, 5 Aug 2011 09:41:49 -0600")
> A section of the stack trace is at the end of this email.
Crash is really in core Emacs (re-display engine may be?) triggered by
Org related things.
It is worth disabling font-lock in Org buffers. I am not sure whether
that would prevent you from making use of any of the Org features.
If you could bisect the Org file and narrow down the crash to a smaller
example file that would be wonderful. Can you give us an idea of number
of scheduled entries per day and how many months they typically span. I
know Org uses cache so may be the performance hit is one time only. May
be there could be a script that populates the cache as part of first
step in the migration process.
Btw, I find the use of "theoretically" a bit inconsistent in your
email. As a developer myself, I wouldn't go to the extent of a writing a
migration assistant just to reap purely "theoretical" benefits. Surely I
am nitpicking here.
Jambunathan K.
next prev parent reply other threads:[~2011-08-06 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 15:41 Converting from OmniFocus to org-mode Jay McCarthy
2011-08-06 10:35 ` Jambunathan K [this message]
2011-08-06 12:48 ` Jay McCarthy
2011-08-15 8:41 ` Bastien
2011-08-06 15:06 ` Sebastien Vauban
2011-08-15 8:42 ` Bastien
2011-08-15 8:37 ` Bastien
2011-08-15 11:32 ` Jay McCarthy
2011-08-15 12:02 ` suvayu ali
2011-08-15 12:09 ` Jay McCarthy
2011-08-15 12:16 ` Suvayu Ali
2011-08-15 12:19 ` Jay McCarthy
2011-08-15 12:50 ` Suvayu Ali
2011-08-15 16:12 ` Jay McCarthy
2011-08-15 16:31 ` suvayu ali
2011-08-15 16:45 ` Nick Dokos
2011-08-15 18:22 ` 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=81d3gibzei.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jay.mccarthy@gmail.com \
/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).