From: Jay McCarthy <jay.mccarthy@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Converting from OmniFocus to org-mode
Date: Sat, 6 Aug 2011 06:48:19 -0600 [thread overview]
Message-ID: <CAJYbDakoMf2rm5R9e88q1QvuuMH68HNi-5TOTpks=RZZ_oEBmA@mail.gmail.com> (raw)
In-Reply-To: <81d3gibzei.fsf@gmail.com>
On Sat, Aug 6, 2011 at 4:35 AM, Jambunathan K <kjambunathan@gmail.com> wrote:
>
>> 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.
I don't want to use it that way, but I can check if it speeds it
up.... and it doesn't make any appreciable difference on the speed and
the crash still happens.
> 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.
% grep -e DEADLINE -e SCHEDULED brain.org | wc -l
462
% grep -e DEADLINE brain.org| sort | head -1
DEADLINE: <2011-08-01 17:00 +1m>
% grep -e DEADLINE brain.org| sort | tail -1
DEADLINE: <2015-09-05 00:00>
% grep -e DEADLINE brain.org| sort | uniq -c | sort | tail -10
3 DEADLINE: <2012-04-01 17:00 +1y>
4 DEADLINE: <2011-08-04 23:00 +1d>
4 DEADLINE: <2011-08-05 17:00 +1d>
4 DEADLINE: <2012-05-01 17:00 +1y>
4 DEADLINE: <2012-09-01 17:00 +1y>
5 DEADLINE: <2011-08-05 17:00 +1w>
5 DEADLINE: <2011-08-06 17:00 +1w>
7 DEADLINE: <2011-09-01 17:00>
8 DEADLINE: <2011-08-05 21:00 +1d>
14 DEADLINE: <2011-09-01 17:00 +1m>
Is this useful information?
> 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.
That sounds like a very good idea.
http://www.google.com/search?q=org-mode%20cache
Only tells me about the caching on the evaluation of code blocks, so
I'm not in a position to implement it, as someone who's never actually
used org-mode.
> 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.
I mean that it seems appealing, but I have no idea because I've never
used it. I need to write a migration assistant before I could even
figure out if there was a benefit.
Jay
--
Jay McCarthy <jay@cs.byu.edu>
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay
"The glory of God is Intelligence" - D&C 93
next prev parent reply other threads:[~2011-08-06 12:48 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
2011-08-06 12:48 ` Jay McCarthy [this message]
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='CAJYbDakoMf2rm5R9e88q1QvuuMH68HNi-5TOTpks=RZZ_oEBmA@mail.gmail.com' \
--to=jay.mccarthy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).