The issue is systematic.
I have changed my settings to:
org-hide-leading-stars nil
org-startup-folded nil
But that doesn't change anything.
I have quasi systematically the issue I described when the file that will be
modified by the capture is not visible when I capture, and generally I don
Hi,
I like the warning in the mode line when the time clocked on a task goes
beyond the effort estimates in the properties drawer.
However, I don’t know how to use this for repeating tasks or habits.
That is, I want to work on a given task every day for less than N
minutes and be warned when goin
reiterating a question I posted to an old thread that may have gotten lost.
Over the summer, commit ded3d27b1468b878197e5fe55a70c5e13350ea27 by Nik
Clayton was merged to master. It's a one-line change that adds new ~~
tags around each lin of code in html export of source blocks. It's useful
becau
Does this answer your question?
#+NAME: tt
| num | ID |
|-+|
| 1 | A |
| 2 | B |
| 3 | C |
| 4 ||
| 5 | E |
#+BEGIN_SRC emacs-lisp :var tt=tt
(length tt)
#+END_SRC
#+RESULTS:
: 5
Best wishes,
Neil
On Wed, 18 Sep 2019 at 18:39, Nathan Neff wrote:
> Hello all,
>
Hello,
I have a source org file that uses tikz (and venndiagram.sty based on
tikz). No problem to export into .tex, but the export into odt and
html fails.
OpenDocument export failed: Wrong type argument: listp, 71
(One more time, I'm working for a publisher who do not knows LaTeX
No comment
On Wed., Sep. 18, 2019, 9:42 p.m. John Kitchin,
wrote:
> You can get an alist of all the properties in an entry with
> org-entry-properties, and then you can let-alist these, or do something
> else. Here is an example that might be related.
>
> * test
> :PROPERTIES:
> :some-random-property: T
