OK, I can confirm that the 20181112 release has this problem but the
development version from github does not.
Thanks,
Jeff
On Sat, Nov 17, 2018 at 12:50 PM Nicolas Goaziou
wrote:
> Hello,
>
> Jeff Trull writes:
>
> > Clocktables containing work in November of 2018 are reported incorrectly,
Clocktables containing work in November of 2018 are reported incorrectly,
showing the wrong day (typically one earlier than the correct date). For
example, in the attached repro.org, work is performed on the 3rd and 5th of
November, but when daily reports are used in the clocktable the work on 5
Sorry, hit C-c C-c in the wrong buffer...
Lele Gaifax writes:
> The local property in the "Work" node is honored by org-columns (C-c C-x
> C-c),
As said, a the local COLUMNS setting is honored by the transient columns view,
but it is ignored by org-clock-report and org-dbclock-update.
Am I
Hi all,
I tried to use a local definition of the COLUMNS property and have a "private"
(that is, not exported to PDF) view of the time spent on something, something
like this:
# -*- coding: utf-8 -*-
#+TITLE: Test local columns
#+COLUMNS: %40ITEM(Item) %13Effort(Effort){:}
#+BEGIN: columnview
Hi Nicolas,
Thanks for your detailed comments. Much appreciated.
> -Original Message-
> From: Nicolas Goaziou
> Sent: den 4 november 2018 23:37
> To: Gustav Wikström
> Cc: emacs-orgmode@gnu.org
> Subject: Re: FW: [RFC] Link-type for attachments, more attach options
>
> Hello,
>
>
Hello,
Marco Wahl writes:
> AFAICT the performance of marking tasks done which contain *a lot* of
> inactive timestams has degraded considerably with this change.
>
> Example:
>
> #v+
> * TODO task
> SCHEDULED: <2018-11-15 .+1d>
> :PROPERTIES:
> :STYLE:habit
> :LAST_REPEAT: [2018-11-14
Hi Ihor,
I'm not sure I follow your suggestion regarding changing the implementation.
But anyhow I don't think the implementation is heavy and at risk of cumbersome
code duplication. My opinion ofc
I like the idea of a function that would symbolically links folders from
"ID"-folder
On Sat, Nov 17 2018, Mark H Weaver wrote:
[...]
>> Ah, system* is a scheme call! So yeah, maybe we could add that call to
>> Geiser's guile initialization... i don't really see how that would cause
>> any problem elsewhere.
>
> I think something like this should be done, not only in the Guile
>
Hello,
Lele Gaifax writes:
> As said, a the local COLUMNS setting is honored by the transient columns view,
> but it is ignored by org-clock-report and org-dbclock-update.
>
> Am I doing something wrong or isn't it possible?
COLUMNS property, or keyword, are not related to clocktable and such.
>> AFAICT the performance of marking tasks done which contain *a lot* of
>> inactive timestams has degraded considerably with this change.
>>
>> Example:
>>
>> #v+
>> * TODO task
>> SCHEDULED: <2018-11-15 .+1d>
>> :PROPERTIES:
>> :STYLE:habit
>> :LAST_REPEAT: [2018-11-14 16:26]
>> :END:
>>
>>
Hello,
Jeff Trull writes:
> Clocktables containing work in November of 2018 are reported incorrectly,
> showing the wrong day (typically one earlier than the correct date). For
> example, in the attached repro.org, work is performed on the 3rd and 5th of
> November, but when daily reports are
Hello,
boris martin writes:
> same issue occured with the master branch of
> https://code.orgmode.org/bzg/org-mode.git
>
> - is there a way for me to know for sure that there is not interference
> from any other git-org
>
> installation file ?
With the minimal init file you provided, I doubt
Hi Gustav,
> I'm not sure I follow your suggestion regarding changing the
> implementation. But anyhow I don't think the implementation is heavy
> and at risk of cumbersome code duplication. My opinion ofc
Sure. The code is not that complicated.
> I like the idea of a function that would
I found there are configuration like this:
#+begin_src emacs-lisp
;;; display org-clock in head-line.
(setq org-clock-clocked-in-display nil)
(defun my/show-org-clock-in-header-line ()
(setq-default header-line-format '((" " org-mode-line-string " "
(defun
14 matches
Mail list logo
