From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jay McCarthy Subject: Re: Converting from OmniFocus to org-mode Date: Sat, 6 Aug 2011 06:48:19 -0600 Message-ID: References: <81d3gibzei.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58865) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QpgIh-0002iG-4V for emacs-orgmode@gnu.org; Sat, 06 Aug 2011 08:48:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QpgIf-0006P0-LO for emacs-orgmode@gnu.org; Sat, 06 Aug 2011 08:48:23 -0400 Received: from mail-yx0-f169.google.com ([209.85.213.169]:39783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QpgIf-0006Os-It for emacs-orgmode@gnu.org; Sat, 06 Aug 2011 08:48:21 -0400 Received: by yxn22 with SMTP id 22so2406330yxn.0 for ; Sat, 06 Aug 2011 05:48:21 -0700 (PDT) In-Reply-To: <81d3gibzei.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K Cc: emacs-orgmode@gnu.org On Sat, Aug 6, 2011 at 4:35 AM, Jambunathan K 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 Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93