> However what Ihor presented is interesting. Do you use similar approach > with shellout and 'emacs -batch' to show currently running task or you > 'push' data from emacs to show it in the taskbar?
I prefer to avoid querying emacs too often for performance reasons. Instead, I only update the clocking info when I clock in/out in emacs. Then, the clocked in time is dynamically updated by independent bash script. The scheme is the following: 1. org clock in/out in Emacs trigger writing clocking info into ~/.org-clock-in status file 2. bash script periodically monitors the file and calculates the clocked in time according to the contents and time from last modification 3. the script updates simple textbox widget using awesome-client 4. the script also warns me (notify-send) when the weighted clocked in time is negative (meaning that I should switch to some more productive activity) Best, Ihor Przemysław Kamiński <p...@intrepidus.pl> writes: > On 9/16/20 9:56 AM, Ihor Radchenko wrote: >>> Wow, another awesomewm user here; could you share your code? >> >> Are you interested in something particular about awesome WM integration? >> >> I am using simple textbox widgets to show currently clocked in task and >> weighted summary of clocked time. See the attachments. >> >> Best, >> Ihor >> >> >> >> >> Marcin Borkowski <mb...@mbork.pl> writes: >> >>> On 2020-09-15, at 11:17, Przemysław Kamiński <p...@intrepidus.pl> wrote: >>> >>>> So, I keep clock times for work in org mode, this is very >>>> handy. However, my customers require that I use their service to >>>> provide the times. They do offer API. So basically I'm using elisp to >>>> parse org, make API calls, and at the same time generate CSV reports >>>> with a Python interop with org babel (because my elisp is just too bad >>>> to do that). If I had access to some org parser, I'd pick a language >>>> that would be more comfortable for me to get the job done. I guess it >>>> can all be done in elisp, however this is just a tool for me alone and >>>> I have limited time resources on hacking things for myself :) >>> >>> I was in the exact same situation - I use Org-mode clocking, and we use >>> Toggl at our company, so I wrote a simple tool to fire API requests to >>> Toggl on clock start/cancel/end: https://github.com/mbork/org-toggl >>> It's a bit more than 200 lines of Elisp, so you might try to look into >>> it and adapt it to whatever tool your employer is using. >>> >>>> Another one is generating total hours report for day/week/month to put >>>> into my awesomewm toolbar. I ended up using orgstat >>>> https://github.com/volhovM/orgstat >>>> however the author is creating his own DSL in YAML and I guess things >>>> were much better off if it all stayed in some Scheme :) >>> >>> Wow, another awesomewm user here; could you share your code? >>> >>> Best, >>> >>> -- >>> Marcin Borkowski >>> http://mbork.pl > > > I don't have interesting code, just standard awesomevm setup. I run > periodic script to output data computed by orgstat and show it in the > taskbar (uses the shellout_widget). > > However what Ihor presented is interesting. Do you use similar approach > with shellout and 'emacs -batch' to show currently running task or you > 'push' data from emacs to show it in the taskbar? > > P.