org-notify dbus send message to KDE/Plasma caused desktop suspend and high
CPU,memory resources.
Here is my config:
```elisp
(setq org-notify-audible nil)
(org-notify-add 'default
'(:time "1h" :period "1h" :duration 8
:actions (-ding -notify/window)
This sounds like an interesting application with a lot of complexities.
It definitely blurs the lines between a database where you could run
queries to find/update records, and a human readable, structured data
file that also does this.
I still don't have a clear grasp on how you structure your da
Thanks Jean for your reply...
On Tue, 10 Sep 2019 at 14:53, Jean Louis wrote:
> [...] It would be nice to write it all in the Org file, yet for me such
> data shall better be in the database. And links are then copied from
> central place to Org files or any other files finally, or to email, or
Thanks Marcin, Bob and John for your interest and replies; I hope you don't
mind me choosing this one to follow up to.
To try to provide a more detailed idea, I've appended below an Org file
that is part documentation sketch, part me trying to remember and write
down what all of my procedures are
> On Sep 9, 2019, at 5:55 PM, akater wrote:
>
> Consider a lisp form that, when evaluated, produces another form. I'm
> used to org printing the resulting form nicely, in lisp blocks. However,
> this is not the case for emacs-lisp src blocks. An example:
>
> 1. The way it should be (and is now t
On Mon, Sep 09 2019, Michaël Cadilhac wrote:
> Is this the expected behavior?
>
> 1. Create an empty org file
> 2. Insert
> * Test
> * Test 2
> 3. With the cursor at Test, hit C-x n s to narrow the view to the Test subtree
> 4. Hit C-c C-s to schedule the line at any date.
>
> As a result, the S
> akater writes:
> Consider a lisp form that, when evaluated, produces another
> form. I'm used to org printing the resulting form nicely, in lisp
> blocks. However, this is not the case for emacs-lisp src
> blocks. An example:
> 1. The way it should be (and is now the c
* John Kitchin [2019-09-09 18:48]:
> It would be helpful to get a better sense of what is the private
> data, e.g. is it something like org-contacts, or some structured
> data in a heading? and what are the workflows that might be generic.
My personal problem is that Org files are scattered aroun
On Tuesday, 10 Sep 2019 at 00:14, Vladimir Nikishkin wrote:
> I am getting the picture, and the circles are where they should be,
> but (!), the arrows are black, which makes them not really visible on
> a black background. How would I either make the background white, or
> (better) just make the f
On Monday, 9 Sep 2019 at 15:17, Michaël Cadilhac wrote:
> Is this the expected behavior?
>
> 1. Create an empty org file
> 2. Insert
> * Test
> * Test 2
> 3. With the cursor at Test, hit C-x n s to narrow the view to the Test
> subtree
> 4. Hit C-c C-s to schedule the line at any date.
>
> As a re
10 matches
Mail list logo
