Re: org-notify: Need to get notifications at the start time of the task (in addition to the deadline)

On Sun, Jun 05 2016, Amit Tendulkar wrote: > I need a way to get notifications at the time of starting a task or at > the start of the meeting (i.e. the SCHEDULED timestamp). Hi Amit, This should work now with the latest version (0.1.1) from ELPA. Cheers, -- Peter signature.asc

Re: [PATCH] patches for org-notify.el

On Sun, Sep 13 2020, Bastien wrote: > you may want to think about a place where you want to host > org-notify.el for the future. code.orgmode.org or github.com, as you prefer. Kind regards, -- Peter

[PATCH] patches for org-notify.el

Hi, Please find attached 2 patches for org-notify.el. Kind regards, -- Peter >From 9ffa89dc99bfe967d9c591948d84dddb2eccdc38 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Peter=20M=C3=BCnster?= Date: Sun, 13 Sep 2020 15:44:00 +0200 Subject: [PATCH 1/2] org-notify.el: Use cl- prefixed

[O] [PATCH]: Replace calls to obsolete macros in org-notify.el

Hi, Please find attached a patch that removes calls to obsolete macros. Kind regards, -- Peter >From 8d2f68f7c01687565dcd248930ab949ab3b77516 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Peter=20M=C3=BCnster?= Date: Mon, 15 Jan 2018 19:23:51 +0100 Subject: [PATCH] Replace

Re: [O] org-notify: can't define an org-notify-add

On Fri, May 22 2015, alain.coch...@unistra.fr wrote: Am I doing something trivially wrong? Any idea how I could debug this? (I have no relevant message in the *Messages* buffer.) Many thanks in advance. Hi, It seems, that the Org Mode developers have not yet applied this patch:

[O] [PATCH] org-notify: Fix compatibility with latest org-element (uppercase properties)

* contrib/lisp/org-notify.el (org-notify-make-todo): Properties from org-element are all uppercase now. * (org-notify-maybe-too-late): Fix typo in docstring (thanks to davemq, https://github.com/p-m/org-notify/issues/3). --- contrib/lisp/org-notify.el | 4 ++-- 1 file changed, 2

Re: [O] Notifications-notify for org-mode scheduled items?

On Mon, Mar 02 2015, Leo Ufimtsev wrote: I would like to receive desktop notifications (1* e.g below) for scheduled items. E.g if I schedule like this: * Make Coffee SCHEDULED: 2015-03-02 Mon 01:30 Then I would like a desktop notification to pup up at 1:30 telling me to make

Re: [O] [PATCH] org-notify: Fix compatibility with latest org-element (uppercase properties)

On Mon, Aug 24 2015, Nicolas Goaziou wrote: Out of curiosity, as org-notify.el's author, don't you have write access into repository? I guess no, but I've never tried... -- Peter

Re: [O] org-clock-select-task: how does it work?

On Sat, Jan 24 2015, Peter Münster wrote: My version is git HEAD and my list is empty. No, it was not HEAD. I did not realise, that my git pull failed because of local changes... Finally, git HEAD is just like 8.2.10. - I get a list with some items, but only very few (only items, where

Re: [O] org-clock-select-task: how does it work?

On Sat, Jan 24 2015, Peter Münster wrote: - I get a list with some items, but only very few (only items, where I've clocked in in this same emacs session). Solved: (setq org-clock-persist 'history) (org-clock-persistence-insinuate) - There are duplicates in the list. Not reproducible

Re: [O] org-clock-select-task: how does it work?

On Sat, Jan 24 2015, Tory S. Anderson wrote: Peter, on my run Org-mode version 8.2.10, I see just what you are describing: a numbered list with the most recent things at the top. Ok, 8.2.10 seems to work. My version is git HEAD and my list is empty. It just doesn't seem to do anything after

[O] org-clock-select-task: how does it work?

Hi, How does this function work please? When I start this function, I get a *Clock Task Select* buffer with the line Recent Tasks and this prompt in the minibuffer: Select task for clocking:. There is no more cursor and whatever I type (TAB for example), I get user-error: Invalid task choice.

[O] bug in org-clock-in-last

Hi, With one prefix-argument, org-clock-in-last calls (org-clock-in (org-clock-select-task)) But it seems, that org-clock-in doesn't expect such an argument. That means, that org-clock-in ignores the selected task. -- Peter

Re: [O] [PATCH 2/2] org-notify: Fix compatibility with latest org-element (uppercase properties)

On Thu, Jun 27 2013, Bastien wrote: * contrib/lisp/org-notify.el (org-notify-make-todo): Properties from org-element are all uppercase now. Mhh... not sure what it means -- do you have a pointer? Yes, here: http://article.gmane.org/gmane.emacs.orgmode/73628 Citation: | (defun

Re: [O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

On Thu, Jun 20 2013, Carsten Dominik wrote: The easiest solution is to simply do nothing, until Org drops support for Emacs 24.2 and earlier. The 'cl' library will be shipped with Emacs for a long time. BTW, which Emacs versions does Org support? Is this documented anywhere? No, but

[O] org-element: property now always uppercase?

Hi, After updating org-mode from git, I noticed, that org-element-parse-buffer uppercases the properties now. Is this a feature or a bug? Example: * TODO test DEADLINE: 2013-06-18 Tue 12:00 :PROPERTIES: :notify: test :END: Result of (org-element-parse-buffer 'headline): (headline

[O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

* contrib/lisp/org-notify.el (org-notify-make-todo) (org-notify-process, org-notify-on-action-button) (org-notify-action-email, org-notify-action-window): Replace `flet' and `macrolet' by `cl-flet' and `cl-macrolet'. --- contrib/lisp/org-notify.el | 10 +- 1 file changed, 5 insertions(+),

[O] [PATCH 2/2] org-notify: Fix compatibility with latest org-element (uppercase properties)

* contrib/lisp/org-notify.el (org-notify-make-todo): Properties from org-element are all uppercase now. --- contrib/lisp/org-notify.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el index 3019852..dd4100d 100644 ---

Re: [O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

On Tue, Jun 18 2013, David Engster wrote: Peter Münster writes: * contrib/lisp/org-notify.el (org-notify-make-todo) (org-notify-process, org-notify-on-action-button) (org-notify-action-email, org-notify-action-window): Replace `flet' and `macrolet' by `cl-flet' and `cl-macrolet'. cl-lib

Re: [O] problem with org-element-parse-buffer

On Mon, Nov 12 2012, Nicolas Goaziou wrote: * TODO test bla bla bla DEADLINE: 2012-11-08 Thu 12:17 In Org, planning info (scheduled, deadline, and closed) must be put just after the headline. Your example isn't valid. Then, org-agenda should ignore that too, shouldn't it? --

Re: [O] problem with org-element-parse-buffer

On Sat, Nov 24 2012, Nicolas Goaziou wrote: Do you want to help basing Agenda on Elements? No, sorry. I don't use the agenda, I prefer push to poll. That's why I wrote org-notify.el. Anyway, the syntax highlighting is a bit permissive too... -- Peter

[O] problem with org-element-parse-buffer

Hi, When using (print (org-element-parse-buffer 'headline)) on this test file: * TODO test bla bla bla DEADLINE: 2012-11-08 Thu 12:17 the output has no information about the deadline with latest git-version. How could I solve this problem please? TIA for any hints, --

[O] [PATCH] Make org-notify.el work with latest org-element.el

* contrib/lisp/org-notify.el (org-notify-convert-deadline): New function. (org-notify-make-todo): Use that function. --- contrib/lisp/org-notify.el | 11 ++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el index

Re: [O] Notifications of appointments in Agenda screen?

On Thu, Aug 30 2012, Nathan Neff wrote: I'm looking all over, and all I can find are posts about how to set up org-notify to call some external messaging app. I'm on OSX and don't want to purchase Growl. Hi, With org-notify.el you don't need an external messaging app, you can do all in

Re: [O] org-notify Tutorial

On Tue, Aug 07 2012, SW wrote: Is a tutorial/guide available for org-notify? Neither of the following were very helpful: http://orgmode.org/worg/org-api/org-notify-api.html http://thread.gmane.org/gmane.emacs.orgmode/52634/focus=52693 On Sat, Aug 25 2012, maroony wrote: Thanks for

Re: [O] Using Org for a dissertation

On Sat, May 12 2012, Richard Lawrence wrote: I am a graduate student in philosophy, and I am about to begin writing my dissertation. I am wondering about whether I should write it in Org, or stick to plain LaTeX. Or in ConTeXt... Sorry, I can't answer your questions about Org-mode. I just

Re: [O] Ever used org-mode contrib packages?

On Wed, Apr 11 2012, François Allisson wrote: I'm curious to know what you are using from org-contrib... - org-notify -- Peter

[O] if featurep then require, why?

Hi, In `org-show-notification', there is --8---cut here---start-8--- (cond [...] ((featurep 'notifications) (require 'notifications) [...] --8---cut here---end---8--- Why is the (require

Re: [O] [RFC] warn time for appointments

On Fri, Mar 23 2012, Nick Dokos wrote: But previously, things were bad enough that I had to turn off the notify process. Now, I'm leaving it on and (mostly) not noticing that it's there, so that's definitely progress. There is still one thing, that we can do: call org-notify-process

Re: [O] [RFC] warn time for appointments

On Fri, Mar 23 2012, Ivan Kanis wrote: I got no reply to my RFC and to my tentative patches. Does that mean everybody is happy with the default 12 minutes warning time? No, I'm not happy with 12 minutes. But there is https://github.com/p-m/org-notify where you can have arbitrary warning times

Re: [O] optimisation of org-notify

On Sun, Feb 26 2012, Peter Münster wrote: On Sun, Feb 26 2012, Nick Dokos wrote: So orgntf-todo-list takes the lion's share of the time but most of it is the 15 calls to org-element-parse-buffer Ok, then I could process only one file at a time. This would divide the processing time by 15

[O] optimisation of org-notify (was: notifications for todo items)

On Sun, Feb 26 2012, Nick Dokos wrote: So orgntf-todo-list takes the lion's share of the time but most of it is the 15 calls to org-element-parse-buffer Ok, then I could process only one file at a time. This would divide the processing time by 15, in your case. But perhaps others would have

Re: [O] notifications for todo items

On Sun, Feb 26 2012, Nicolas Goaziou wrote: I didn't look at the code but you probably mean (org-element-parse-buffer 'headline) if you're only interested in headline data. Yes, it's headline in the code... :) -- Peter

Re: [O] notifications for todo items

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

Re: [O] notifications for todo items

On Thu, Feb 23 2012, Nick Dokos wrote: what does this do that appt.el (and its org interface) does not? Sorry, I've totally forgotten to write about my motivation, to create such an org-notify module. Here a summary: - different warning periods for different todo-types - fine grained warning

Re: [O] patch for warning time (first baby sted)

On Sun, Feb 19 2012, Ivan Kanis wrote: This patch implements warn time for org appt. It only works on emacs bzr (the variable appt-warning-time-regexp appears in it). You need to add the warntime in the text of the entry, like so : * doctor warntime 10 2012-02-19 10:00 If you change it

[O] notifications for todo items

Hi, I've written a module, that allows flexible notifications for todo items with deadline: http://pmrb.free.fr/work/OS/org-notify.el Feedback is welcome! -- Peter

[O] get all todo items as lisp list

Hi, Given a todo list in an org file, is there already a function, that converts this list to an elisp list, that contains at least heading, deadline and properties? Example input: --8---cut here---start-8--- * TODO todo-test DEADLINE: 2012-04-19 Thu 13:33

[O] [PATCH] Avoid some warnings about `assignment to free variable'

* lisp/org.el, lisp/org-pcomplete.el: Add some `defvars' to avoid warnings about `assignment to free variable'. TINYCHANGE --- lisp/org-pcomplete.el |5 + lisp/org.el |2 ++ 2 files changed, 7 insertions(+), 0 deletions(-) diff --git a/lisp/org-pcomplete.el

Re: [O] [PATCH] Avoid lisp error with (org-deadline nil +1d)

On Thu, Nov 24 2011, Nick Dokos wrote: Are they free variable warnings? If so, you now know how to fix them: go wild :-) All right, done so... ;) -- Peter

Re: [O] [PATCH] Avoid lisp error with (org-deadline nil +1d)

On Wed, Nov 23 2011, Carsten Dominik wrote: Fixed, thanks, please verify. Verified: ok, thanks. Is `(defvar parse-time-weekdays)' still needed then? And if yes, why? -- Peter

Re: [O] [PATCH] Avoid lisp error with (org-deadline nil +1d)

On Wed, Nov 23 2011, Nick Dokos wrote: Generally speaking, defvars like this tell the compiler to shut up about the free variable. You can see if it is needed, by commenting out the defvar and then trying to compile the file. Indeed, now there are 30 warnings instead of only 29 ... ;) Thanks

Re: [O] How to say I did that yesterday?

On Tue, Nov 22 2011, Dave Abrahams wrote: I often discover that I completed something a few days ago and I would like to mark it done with the appropriate date as though I had marked it done in the past. That means, e.g., for a repeating event it might repeat sooner than if it had been done

Re: [O] [PATCH] Avoid lisp error with (org-deadline nil +1d)

On Tue, Nov 22 2011, Carsten Dominik wrote: This is not allowed, we cannot define a variable defined in another package. Oh, pardon. Can you send a backtrace of the error, please? Of course (from emacs -Q): --8---cut here---start-8--- Debugger

[O] [PATCH] Timestamps: Fix org-schedule and org-deadline with absolute time arguments

* lisp/org.el (org-add-planning-info): Treat absolute time too. TINYCHANGE --- lisp/org.el |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index fffb0c1..3342b87 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -12078,9 +12078,8 @@ be

[O] [PATCH] Avoid lisp error with (org-deadline nil +1d)

* lisp/org.el (parse-time-weekdays): Must not be void. TINYCHANGE --- lisp/org.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 253703b..41d418a 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -15229,7 +15229,7 @@ user. (setq

Re: [O] enhancements for org-agenda-to-appt

On Tue, Nov 08 2011, Daniel Clemente wrote: 1.) Warning period should be taken from timestamp That means, that the warntime must be passed to appt-add. 2.) Warning period in hours and minutes -3h for 3 hours or -10M for 10 minutes should be possible. Do you really need to

[O] enhancements for org-agenda-to-appt

Hello, Before enhancing org-agenda-to-appt (and some other parts) to fit my needs, I would like to get some feedback for my ideas: - General opinions about the ideas. - Hints about already existing usable code. - Hints how to implement the ideas with the least effort. The general idea is, to get

Re: [O] notify, when something to do

On Sun, Oct 23 2011, Bastien wrote: - Perhaps the main problem: appt does not know about warning periods. There are items with -3d, other with -5M[1]. There is only one universal appt-message-warning-time. Would it be possible, to have a individual warning-time for each todo-item,

[O] [PATCH] Agenda: Allow filter list without category in org-agenda-to-appt

Hello, Here the output of git format-patch master. I hope it's correct, it was my first git-commit... --8---cut here---start-8--- From 82da273bb0884347762e883786b334302ad3f0cd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Peter=20M=C3=BCnster?= p...@free.fr Date:

Re: [O] org-contacts or bbdb?

Thank you all for your points of view! So I'll try bbdb-3. (I've already started a bit.) On Fri, Oct 21 2011, Eric Abrahamsen wrote: As Rasmus mentioned, if you use BBDB you should get version 3, it's significantly better than the previous version. There's a slow movement towards better

[O] notify, when something to do

Hello, I would like to be notified[1], when a todo item enters the warning period, scheduled time, or deadline. I can imagine writing a function, that executes every 5 minutes, that scans all agenda files calling `org-get-[scheduled,deadline]-time', but I hope, that there is already something,

Re: [O] notify, when something to do

On Sun, Oct 23 2011, Tassilo Horn wrote: pmli...@free.fr (Peter Münster) writes: I would like to be notified[1], when a todo item enters the warning period, scheduled time, or deadline. I export my org entries as appt alarms, so that I get system notifications 15 minutes before meetings

[O] patch: accept lazy filter in org-agenda-to-appt

Hello, I use `org-agenda-to-appt' this way: --8---cut here---start-8--- (org-agenda-to-appt t '((headline TODO))) --8---cut here---end---8--- But this works only with the following patch: --8---cut

Re: [O] patch: accept lazy filter in org-agenda-to-appt

Hello, The following patch replaces the previous one: --8---cut here---start-8--- === modified file 'lisp/org/org-agenda.el' --- lisp/org/org-agenda.el 2011-09-02 16:38:40 + +++ lisp/org/org-agenda.el 2011-10-23 20:03:11 + @@ -8415,10

[O] org-contacts or bbdb?

Hello, I would like to manage my contacts, so that I can - easily search them - add new email addresses from gnus (summary buffer) - complete email addresses in gnus (message buffer and prompts in mini-buffer) - and perhaps more in the future Could you guide me please, what to choose,