On Friday, 12 May 2017 at 18:06, Joe Corneli wrote:
> On Fri, May 12, 2017 at 4:37 PM, Nicolas Goaziou
> wrote:
>
>
>> I'm not convinced it is worth changing the syntax class of "'" or even
>> making a special case for "'". You can get rid of this problem using
>> \(P\) instead.
>
> Thanks for su
On Fri, May 12, 2017 at 4:37 PM, Nicolas Goaziou wrote:
> I'm not convinced it is worth changing the syntax class of "'" or even
> making a special case for "'". You can get rid of this problem using
> \(P\) instead.
Thanks for suggesting this work around, I didn't know that bit of syntax!
-Jo
Hello,
Joe Corneli writes:
> With the test file as follows:
> ==
>
> #+TITLE: example
> #+AUTHOR:Joe Corneli
>
> #+DATE: May 12, 2017
> #+DESCRIPTION: example
>
> #+LANGUAGE: en
> #+OPTIONS: H:3 num:t toc:t \n:nil @
Hello,
Roland Everaert writes:
> Since this morning my clocktable doesn't fill a column related to a
> property, any known issue and workaround/fix for this?
I think this one is fixed in development version. You may want to update
Org.
Regards,
--
Nicolas Goaziou
Hello,
Rainer Stengele writes:
> I have a wrong clock summary in my agenda and also in clock tables
> since 9.0.6. Also the clock sum format suddenly includes days instead
> of only hours as before.
>
> I have a function overriding the agenda clocktable report - see below.
> What has changed in
Am 08.05.2017 um 12:31 schrieb Roland Everaert:
I just see this.
Since this morning my clocktable doesn't fill a column related to a
property, any known issue and workaround/fix for this?
Regards,
On Mon, May 8, 2017 at 10:37 AM, Eric S Fraga mailto:e.fr...@ucl.ac.uk>> wrote:
On Sunday,
With the test file as follows:
==
#+TITLE: example
#+AUTHOR:Joe Corneli
#+DATE: May 12, 2017
#+DESCRIPTION: example
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
#+OPTIONS: TeX:t L
Hello,
Kyle Meyer writes:
> Yeah, in order to make org-sort-entries, org-sort-list, and
> org-table-sort-lines behave the same way with respect to how they read
> getkey-func and compare-func, I ignored the warning in
> called-interactively-p's docstring that says it can be "brittle" if a
> func
