Hi,
I got a few questions regarding `org-agenda-list`, I hope this is the right
place to ask about them.
First of some background to my problem. I've been using org-agenda-super to
group my things in the agenda view, for example all todos for that day into
one group, all low priority into another
Hi,
There seems to be an inconsistency between the Org syntax spec and the
actual behavior regarding text markup: the spec forbids `,`, `'` and
`"` in the border, yet it seems to work just fine to use them there in
the current version of Org. I think it's great that Org mode supports
this, but sin
Makes sense. IMO it'd be nice to see something along the lines
of this
explanation in the commit message itself.
The function name is missing here:
* lisp/org.el (org-get-cursor-date): ...
To my eyes, the new variable doesn't add any clarity over
keeping it
inline.
Addressed in att
Thanks for the patch.
No Wayman writes:
> The regular expression in `org-get-cursor-date' assumes the time
> grid string will have two digits in the hour portion of the time
> strng.
> However, the grid time string does not always have two digits. For
> example:
>
> " 8:00.."
Makes sense.
Hello,
I noticed this while using `org-resolve-clocks' when
`org-clock-continuously' was set to true.
Let's say I clock into "Task 1" at 12:00, and then at 12:30, I start
working on "Task 2". Then, at 12:45, I notice that I forgot to clock out
of "Task 1". No worries, org-mode has `org-resolve-cl
Kévin Le Gouguec writes:
> Huh. Based on the discussion for bug#37774[1][2][3][4], I had assumed
> this kind of kludge would be necessary, but both Emacs 25.3 and 26.3
> seem to evaluate and byte-compile the following snippet with no errors:
>
> #+begin_src elisp
> (defface foobar '((t (:extend t
Kyle Meyer writes:
>> +(defmacro org--extended-face (attributes)
>> + "Make face that extends beyond end of line.
>> +
>> +Up to Emacs 26, all faces extended beyond end of line; getting
>> +the same behaviour starting with Emacs 27 requires :extend t."
>> + `(nconc ,attributes (when (>= emacs-m
Hi,
There seems to be an inconsistency between the Org syntax spec and the
actual behavior regarding text markup: the spec forbids `,`, `'` and
`"` in the border, yet it seems to work just fine to use them there in
the current version of Org. I think it's great that Org mode supports
this, but sin
