Re: [BUG] clocktable match doesn't seem to support matching items based on parent property [9.6.15 (release_9.6.15 @ /snap/emacs/current/usr/share/emacs/29.3/lisp/org/)]

"Felix H. Dahlke" writes: > I want to create a clocktable report for all items under a specific > heading, using the match keyword and the ITEM property. It appears > that matching items this way won't include any subheadings, therefore > not showing their times in the clocktable. It is expected

[BUG] clocktable match doesn't seem to support matching items based on parent property [9.6.15 (release_9.6.15 @ /snap/emacs/current/usr/share/emacs/29.3/lisp/org/)]

I want to create a clocktable report for all items under a specific heading, using the match keyword and the ITEM property. It appears that matching items this way won't include any subheadings, therefore not showing their times in the clocktable. My guess would be that agenda and clocktable shar

[FR] Transfer export attributes from dynamic block to its first child (was: Bug: clocktable)

writes: > J’ai un soucis avec le clocktable qui semble être un bug car il n’accepte > pas les attributs latex avant la ligne BEGIN: > #+ATTR_LATEX: :align Xll :width \textwidth > #+BEGIN: clocktable :scope file :maxlevel 2 This is a commonly reported problem - when using dynamic blocks (in pa

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

OK, got it now, thanks! I confirmed everything you said. My takeaway is that instead of using global properties as a single property at the top level, I should create a top-level properties drawer, which will have immediate usability. In the case of my example that would be: C-u C-c C-x d HOURLY

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Jeff Trull writes: > Yes, I can make it work now - but only after reloading it at least one time > from disk. > > When I type it in for the first time, it doesn't work. I have to save, then > (revert-buffer). > ... > Also, if you change the value (say, from 150 to 210) the old value persists > un

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Yes, I can make it work now - but only after reloading it at least one time from disk. When I type it in for the first time, it doesn't work. I have to save, then (revert-buffer). In other words, in a fresh buffer, paste all the above, then hit C-c C-c on the BEGIN line. The global properties don'

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Jeff Trull writes: > I just confirmed that it is still doing this (Emacs 28.2, org 9.5.5). The > result looks the same as before: > > #+BEGIN: clocktable :scope file :maxlevel 2 :properties ("HOURLY_RATE") > :inherit-props t > #+CAPTION: Clock summary at [2022-10-17 Mon 16:50] > ... > Note that t

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

I just confirmed that it is still doing this (Emacs 28.2, org 9.5.5). The result looks the same as before: #+BEGIN: clocktable :scope file :maxlevel 2 :properties ("HOURLY_RATE") :inherit-props t #+CAPTION: Clock summary at [2022-10-17 Mon 16:50] | HOURLY_RATE | Headline | Time | | |---

Re: Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Jeff Trull writes: > :inherit-props seems to not consider global properties. > > Testcase: I am unable to reproduce on the latest main. The inherited properties are displayed as expected on my side. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG] Clocktable hides agenda buffer due to window manipulation in org-string-width [9.6 (9.6-??-e9da29b6f @ /Users/tok/.emacs.d/.local/straight/build-28.1/org/)]

> Are you able to reproduce starting from emacs -Q? > See https://orgmode.org/manual/Feedback.html In fact, I'm not. So I guess there's something in my configuration conflicting with this function. I'll have to find out what it is. Thanks for pointing this out, and sorry for bothering you. Best

Re: [BUG] Clocktable hides agenda buffer due to window manipulation in org-string-width [9.6 (9.6-??-e9da29b6f @ /Users/tok/.emacs.d/.local/straight/build-28.1/org/)]

Tobias Kniep writes: > Observation: > When activating clocktable mode in agenda view > (e.g. by pressing "R"), the current window switches to a previous > buffer and thus hides the agenda. I can manually switch back to the > agenda buffer and the clocktable is displayed. However, any > redrawing

[BUG] Clocktable hides agenda buffer due to window manipulation in org-string-width [9.6 (9.6-??-e9da29b6f @ /Users/tok/.emacs.d/.local/straight/build-28.1/org/)]

Observation: When activating clocktable mode in agenda view (e.g. by pressing "R"), the current window switches to a previous buffer and thus hides the agenda. I can manually switch back to the agenda buffer and the clocktable is displayed. However, any redrawing of the agenda (e.g. when moving to

Re: [BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

> Jeff Trull writes: > Confirmed, after updating org it now works! Thanks for your help. > On Tue, Nov 30, 2021 at 1:07 AM Colin Baxter 😺 wrote: >> Hello Jeff >> >> You clock table works for me, including your missing rate of >> 150. I attach a screen shot. >>

Re: [BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Confirmed, after updating org it now works! Thanks for your help. On Tue, Nov 30, 2021 at 1:07 AM Colin Baxter 😺 wrote: > Hello Jeff > > You clock table works for me, including your missing rate of 150. I > attach a screen shot. > > By the way, you have a ":inherit-props t" which is not on the #

Re: [BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Hello Jeff You clock table works for me, including your missing rate of 150. I attach a screen shot. By the way, you have a ":inherit-props t" which is not on the #+BEGIN: clocktable line. I assume that has been corrupted in the email formatting. Best wishes

[BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

:inherit-props seems to not consider global properties. Testcase: # Create a global property #+PROPERTY: HOURLY_RATE 150 * Top 1 ** Sub 1A # here we should get the global property, but do not :LOGBOOK: CLOCK: [2021-09-26 Sun 12:25]--[2021-09-26 Sun 13:25] => 1:00 - I did some tasks

Bug: clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

:inherit-props seems to not consider global properties. Testcase: # Create a global property #+PROPERTY: HOURLY_RATE 150 * Top 1 ** Sub 1A # here we should get the global property, but do not :LOGBOOK: CLOCK: [2021-09-26 Sun 12:25]--[2021-09-26 Sun 13:25] => 1:00 - I did some tasks

Bug: clocktable latex attributes

Hi the Orgmode team, I have a problem with the clocktable which seems to be a bug because it does not accept latex attributes before the BEGIN line:#+latex_header: \usepackage{tabularx}#+ATTR_LATEX: :align Xll :width \textwidth#+BEGIN: clocktable :scope file :maxlevel 2 the only solution I foun

Bug: clocktable

Salut l’équipe d’Orgmode, J’ai un soucis avec le clocktable qui semble être un bug car il n’accepte pas les attributs latex avant la ligne BEGIN: #+latex_header: \usepackage{tabularx} #+ATTR_LATEX: :align Xll :width \textwidth #+BEGIN: clocktable :scope file :maxlevel 2 la seul solution que j'a

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

I am also experiencing this issue. I'm assuming =org-agenda-sticky= is set to =t= in your configuration since that is what I have in mine. I've tracked the problem down to (1) the handling of =org-agenda-sticky= in =org-agenda-goto-date=, (2) how this affects what =org-agenda-mode= (called by =o

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

Does anyone have an idea of why this problem occurs? And perhaps how to fix it? On 3/4/19 7:02 PM, Bernt Hansen wrote: > Actually I think it is a bug. This weird behaviour has been around for > a very long time (years probably). > > I have noticed similar behaviour with log mode, and clock check

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

Actually I think it is a bug. This weird behaviour has been around for a very long time (years probably). I have noticed similar behaviour with log mode, and clock check mode as well. I can reproduce the issue at with the following recipe: C-c a a (start org agenda) j -3 RET (go back 3 days alt

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

This is crazy!  After months of problems, I myself no longer can reproduce this issue!  :-/ Comments welcome (Please!) ... but this issue no longer is actually a bug.  On 3/4/19 3:22 PM, Daniel Ortmann wrote: > Remember to cover the basics, that is, what you expected to happen and > what in fact

[O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen.  You don't know how to make a good report?  See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. -

Re: [O] Bug: clocktable thinks Oct 29 is Oct 28 [9.1.14 (release_9.1.14-1012-g643481 @ /home/unhammer/src/org-mode/lisp/)]

Kevin Brubeck Unhammer čálii: [...] > I see the same on org-mode > 9.1.9 (bundled with Emacs 26.1) or 9.1.12 and 9.1.14 from melpa-stable, > gnu elpa. > > I do *not* see this in 8.2.10 bundled with Emacs 25.3.2. git bisect tells me 8c7a14a850e7b988fe4c9d0eea9207793e2af368 introduced this. si

[O] Bug: clocktable thinks Oct 29 is Oct 28 [9.1.14 (release_9.1.14-1012-g643481 @ /home/unhammer/src/org-mode/lisp/)]

Hi, I did $ git clone https://code.orgmode.org/bzg/org-mode.git (which got me 643481fade386aa51d88ccc22b9669b0b77daaa1 ) $ cd org-mode $ make autoloads $ emacs -Q -l /tmp/init.el /tmp/foo.org where /tmp/init.el has: (add-to-list 'load-path "~/src/org-mode/lisp") (require 'org) and /tmp/foo.

Re: [O] Bug: clocktable question [9.1.6 (9.1.6-dist @ /Users/savoie/tmp/org-bug/org-9.1.6/lisp/)]

Hello, sav...@nsidc.org writes: > - GNU Emacs 25.2.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version > 10.9.5 (Build 13F1911)) of 2017-04-21 > - Org mode version 9.1.6 (9.1.6-10-g0c9329-elpa @ > /Users/savoie/.emacs.d/elpa/org-20180108/) > > Having a hard time understanding clocktables.

[O] Bug: clocktable question [9.1.6 (9.1.6-dist @ /Users/savoie/tmp/org-bug/org-9.1.6/lisp/)]

- GNU Emacs 25.2.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 10.9.5 (Build 13F1911)) of 2017-04-21 - Org mode version 9.1.6 (9.1.6-10-g0c9329-elpa @ /Users/savoie/.emacs.d/elpa/org-20180108/) Having a hard time understanding clocktables. I either have a bug or a misunderstanding. W

Re: [O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

Hello, Dale Sedivec writes: > Thank you as always Nicolas! You fixed the time zone for :tstart in > 60eda8e4ec4. However, I think the parsing of :tend (locally bound as te) > eight lines below that needs the same fix. Oops! Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

On Mon, Jul 10, 2017 at 3:59 AM, Nicolas Goaziou wrote: > Hello, > > Dale Sedivec writes: > [...] > > I notice that as of 112c5ba479d, org-clocktable-steps parses :tstart and > > :tend with the ZONE argument to org-parse-time-string as T. I think this > > is causing org-parse-time-string to pa

Re: [O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

Hello, Dale Sedivec writes: > Hi! I think clocktables may be parsing time zones incorrectly in :tstart > and :tend, leading to incorrect output. Steps to reproduce: > > 1. Start a fresh Emacs within that same along the lines of: > > ~~ > mkdir /tmp/emacs > TZ=America/Chicago HOME=/tmp/emac

[O] Bug: clocktable interprets tstart/tend incorrectly, maybe? [9.0.9 (9.0.9-636-gd39ccc-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170709/)]

Hi! I think clocktables may be parsing time zones incorrectly in :tstart and :tend, leading to incorrect output. Steps to reproduce: 1. Start a fresh Emacs within that same along the lines of: ~~ mkdir /tmp/emacs TZ=America/Chicago HOME=/tmp/emacs /path/to/emacs ~~ I *think* setting TZ

Re: [O] Bug: clocktable doesn't preserve formulas with :scope file-with-archives

Hello, Dale writes: > Hi! I've found that the "#+TBLFM:" in a clocktable can get changed or > deleted when used together with ":scope file-with-archives". Here's a > minimal org file to reproduce with: > > --8<-- > * Test > :LOGBOOK: > CLOCK: [2016-10-20 Thu 17:42]--[2016-10-20 Thu 18:

[O] Bug: clocktable doesn't preserve formulas with :scope file-with-archives

Hi! I've found that the "#+TBLFM:" in a clocktable can get changed or deleted when used together with ":scope file-with-archives". Here's a minimal org file to reproduce with: --8<-- * Test :LOGBOOK: CLOCK: [2016-10-20 Thu 17:42]--[2016-10-20 Thu 18:03] => 0:21 :END: #+BEGIN: clocktabl

[O] Bug: Clocktable does not count columns for properties when using :formula % [8.3.3 (8.3.3-elpaplus @ /home/fvaresi/.emacs.d/elpa/org-plus-contrib-20160108/)]

Hi there! Let me first introduce a test case. Example content: === * DONE Task A :tag1: CLOCK: [2016-01-09 Sat 04:36]--[2016-01-09 Sat 05:20] => 0:44 * DONE Task B :tag2: CLOCK:

Re: [O] Bug: clocktable does not respond to :wstart [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/local/Cellar/emacs/24.3/share/emacs/24.3/lisp/org/)]

Hi Bastien, Upgraded org-mode - problem gone! Thank you! Torben On 19 April 2014 07:28, Bastien wrote: > Hi Torben, > > torben.leh...@gmail.com writes: > > > Package: Org-mode version 7.9.3f > > I can reproduce the bug with this version, but it has been fixed in > the meantime and Org version

Re: [O] Bug: clocktable does not respond to :wstart [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/local/Cellar/emacs/24.3/share/emacs/24.3/lisp/org/)]

Hi Torben, torben.leh...@gmail.com writes: > Package: Org-mode version 7.9.3f I can reproduce the bug with this version, but it has been fixed in the meantime and Org version > 8 works fine. See the manual on how to install non built-in Org : http://orgmode.org/manual/Installation.html Thanks,

[O] Bug: clocktable does not respond to :wstart [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/local/Cellar/emacs/24.3/share/emacs/24.3/lisp/org/)]

I'm trying to get a weekly clocktable report starting on Sunday using this specification: #+BEGIN: clocktable :maxlevel 2 :scope agenda-with-archives :wstart 2 :block thisweek-1 :step day :fileskip0 :narrow 20! #+END: The problem is that no matter which argument I use for :wstart the report st

[O] [BUG] Clocktable error with multiple source files from parent dir

Hello, While generating a clock table report with source data in files from the current directory works, it does not work if there are *more than one* such source file in the parent directory. Yes, I known, the description is strange... Though, it seems to be the criteria... ECM and recipe: 1. S

[Orgmode] Bug: clocktable :link often jumps to wrong target [6.36c]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. --