From: Carsten Dominik <email@example.com> To: Samuel Wales <firstname.lastname@example.org> Cc: email@example.com Subject: Re: footnote bug Date: Mon, 30 Mar 2009 17:38:57 +0200 [thread overview] Message-ID: <C7B43C79-E0AC-46FF-A339-BF4BE67FA002@gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Samuel, caching stuff for the agenda would mean rewriting the agenda code. Do you have more detailed pointers what operations exactly are slow? Maybe we can profile and improve these without resorting to cacheing. - Carsten On Mar 26, 2009, at 9:21 PM, Samuel Wales wrote: > The following source produces the following output. > > ************* sorting speed >>> The agenda is wonderful for other stuff, but for me it is >>> not an editing mode per se. I have never been able to use >>> the agenda for full control over the org file, as some >>> people are able to do. For me (at least on my computer) it >>> is slow. >> >> What is "slow". Maybe we can improve things? > > You could use cached values for agenda files whose last > update time is earlier than the last agenda scan. That > could lead to significant speedups for people who have > several agenda files.[fn:15] > > [fn:15] It wouldn't help with people who have a single > agenda file, and it wouldn't help with people who very > frequently use all of their agenda files. For those use > cases, something much more complicated and brittle would > probably be necessary > > > Output: > > You could use cached values for agenda files whose last > update time is earlier than the last agenda scan. That > could lead to significant speedups for people who have > several agenda files. > [fn:15] It wouldn't help with people who have a single > agenda file, and it wouldn't help with people who very > frequently use all of their agenda files. For those use > cases, something much more complicated and brittle would > probably be necessary >  [fn:15] > > -- > Myalgic encephalomyelitis denialism is causing death (decades early; > Jason et al. 2006) and severe suffering (worse than nearly all other > diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting > science. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacsemail@example.com > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-03-30 16:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-26 20:21 Samuel Wales 2009-03-30 15:38 ` Carsten Dominik [this message] 2009-04-02 5:53 ` Samuel Wales 2009-04-02 7:06 ` Carsten Dominik 2009-04-06 4:50 ` Samuel Wales
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=C7B43C79-E0AC-46FF-A339-BF4BE67FA002@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: footnote bug' \ /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
Code repositories for project(s) associated with this 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).