On 2019-09-11, at 01:11, John Kitchin wrote:
> 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.
This
On 2019-09-10, at 23:49, Neil Jerram wrote:
> One might then think: why still be in Org mode? As opposed to a
> traditional database. [...]
Why not both?
Did anyone consider writing a foreign data wrapper (see
e.g. https://wiki.postgresql.org/wiki/Foreign_data_wrappers) so that
PostgreSQL c
Neil,
You could use transient[1], the tool used to build the menus of magit[2].
I really like magit's discoverability and ease of use.
There is a video of a talk where it is used to control kubernetes from
inside emacs in magit style:
https://www.youtube.com/watch?v=w3krYEeqnyk
[1] transient: ht
This problem started for me a little while ago: images generated from R source
blocks no longer appear even though I have images display turned on.
For example, this file:
# -
#+begin_src R :results graphics file :file /tmp/src.png
x <- seq(-4, 4, length=200)
y <- dnorm(x, mean=0, sd=1)
pl
William Denton writes:
> This problem started for me a little while ago: images generated from R
> source
> blocks no longer appear even though I have images display turned on.
>
> For example, this file:
>
> # -
>
> #+begin_src R :results graphics file :file /tmp/src.png
> x <- seq(-4, 4,
"numbch...@gmail.com" writes:
> 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
>
Attached is a patch to allow one to specify that results from executing a
block should go to a specific buffer.
When a :buffer is specified, output goes to that buffer, which is erased
first, e.g.:
#+begin_src sh :results buffer :buffer *foo*
echo foo
#+end_src
When no :buffer is specified