p-m / org-notify Goto Github PK

Hello!

With this commit, org-notify is no longer in org-contrib: https://git.sr.ht/~bzg/org-contrib/commit/c6aef31ccfc7c4418c3b51e98f7c3bd8e255f5e6 , so I wanted to request org-notify to be packaged in either elpa or melpa.

I got a strange problem. If I press a button at the notification window like DONE, SHOW, ... a new browser window will open leading to dropbox.com.

Maybe that's why my org files are stored in my dropbox folder?

Hi,

Thanks for that package.

I was thinking of adding some kind of reminder features to my setup as well. However, I'd like to stay flexible and low-profile.

Flexible: not every appointment does have the same requirements related to notifications. For example, for one appointment, I just need to be briefly prepared, so a five minute reminder is appropriate. For another appointment, I need to bike to a different location which takes 25 minutes to do so. So I need a 35 minute reminder.

Low-profile: with capture, yankpad and similar, handling of properties might be really easy. However, I personally do prefer tags for assigning meta-data for reminders. For the examples above, I would prefer simply tagging with rem5 and rem35 respectively in order to get notifications five and 35 minutes before the associated events do start. This way, I can use pre-defined tags quickly.

For longer period reminders, I'd add the usual abbevations: rem3d (three days), rem2m (two months), and so on.

I know that this is a bold idea to post here in this package since it already introduced a different implementation idea. However, I just want to give food for thought and maybe some day, org-notify will provide both methods to define notifications.

"warning" is misspelled as "waring" at line 138 of org-notify.el.

Would you please give me a short example of an todo item showing the configuration of org-notify.el? The two hints at org-notify.el:

;; (require 'org-notify)
;; (org-notify-start)

;; Example setup:
;; (org-notify-add 'appt
;; '(:time "-1s" :period "20s" :duration 10
;; :actions (-message -ding))
;; '(:time "15m" :period "2m" :duration 100
;; :actions -notify)
;; '(:time "2h" :period "5m" :actions -message)
;; '(:time "3d" :actions -email))

doesn't help very much.

Hi, GNU ELPA can't track the upstream code any more because it has diverged. This is probably the result of a force-push on your upstream repository or something like that:

% make fetch/org-notify              
emacs --batch -l admin/elpa-admin.el -f elpaa-batch-fetch-and-show "org-notify"
Fetching updates for org-notify...
Upstream of org-notify has DIVERGED!

  Local changes:
bbd9a049ff  [email protected]       No more need to prefix actions with a hyphen

  Upstream changes:
dbb2347fb4  [email protected]       Make use of the function ensure-list in org-notify-process

%

In order for GNU ELPA to track your changes, it has to be able to "fast-forward", so you need to merge the bbd9a04 commit into your upstream tree, e.g.:

cd .../where/you/keep/your/clone/of/org-notify
git fetch git://git.sv.gnu.org/emacs/elpa.git externals/org-notify
git merge FETCH_HEAD

Hi,
org-notify is great, I use it a lot. But I just found org-notify package missing, it seems this package were in org-contrib, but now it seems it is removed? And neither can I find it in melpa, so what is the status of this package? Will it keep alive in the long run?