From: "Peter Münster" <pmlists@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: notifications for todo items
Date: Sun, 26 Feb 2012 01:09:03 +0100 [thread overview]
Message-ID: <87k43a5ucg.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: 12871.1330128535@alphaville
On Sat, Feb 25 2012, Nick Dokos wrote:
> A quick first impression: orgntf-process seems expensive. It seems
> to take 100% of one core (I've got a quad-core processor) for three or
> four seconds every fifty seconds. Unfortunately, the core is the same one
> that's running emacs, so emacs stops responding for those three or four
> seconds. I have disabled org-notify for now.
How many lines do you have in your org-files?
(I've about 200 and execution time is about 100ms.)
I call now "(org-element-parse-buffer 'heading)", I hope it's faster for
you. Is it faster, when the file is byte-compiled?
Other ideas:
- I could divide orgntf-process into several tasks, so that things run
more smoothly.
- You could call (org-notify-start -60), so the process will be called,
when idle for one minute.
The file has a new home: https://github.com/p-m/org-notify
There is now `orgntf-verbose' to see execution time of
`orgntf-todo-list'.
Thanks for testing!
--
Peter
next prev parent reply other threads:[~2012-02-26 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 23:38 notifications for todo items Peter Münster
2012-02-23 1:28 ` Nick Dokos
2012-02-23 8:36 ` Peter Münster
2012-02-23 9:06 ` Nick Dokos
2012-02-25 0:08 ` Nick Dokos
2012-02-26 0:09 ` Peter Münster [this message]
2012-02-26 2:45 ` Nick Dokos
2012-02-26 5:04 ` Nick Dokos
2012-02-26 14:06 ` optimisation of org-notify (was: notifications for todo items) Peter Münster
2012-03-04 23:37 ` optimisation of org-notify Peter Münster
2012-02-26 9:33 ` notifications for todo items Nicolas Goaziou
2012-02-26 14:07 ` Peter Münster
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=87k43a5ucg.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--cc=emacs-orgmode@gnu.org \
/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.