Re: is this a known issue in clocktable output?
On Sat, Nov 30, 2019 at 1:05 AM Marco Wahl wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.emacs.orgmode as well. > > Soubzriquet writes: > > > I'm new to using org-mode for time tracking, and have run into an odd > issue > > with using "day" steps where the date is getting offset sometimes. > > > > I saw the issue with 26.1, was not fixed by updating to current > > environment with an empty init.el on OS X: > > [...] > > > * Day 1 > > :LOGBOOK: > > CLOCK: [2019-11-01 Fri 10:00]--[2019-11-01 Fri 11:00] => 1:00 > > :END: > > * Day 2 > > :LOGBOOK: > > CLOCK: [2019-11-02 Sat 10:00]--[2019-11-02 Sat 12:00] => 2:00 > > :END: > > * Day 3 > > :LOGBOOK: > > CLOCK: [2019-11-03 Sun 10:00]--[2019-11-03 Sun 13:00] => 3:00 > > :END: > > * Day 4 > > :LOGBOOK: > > CLOCK: [2019-11-04 Mon 10:00]--[2019-11-04 Mon 14:00] => 4:00 > > :END: > > * Day 5 > > :LOGBOOK: > > CLOCK: [2019-11-05 Tue 10:00]--[2019-11-05 Tue 15:00] => 5:00 > > :END: > > * Day 6 > > :LOGBOOK: > > CLOCK: [2019-11-06 Wed 10:00]--[2019-11-06 Wed 16:00] => 6:00 > > :END: > > > > #+BEGIN: clocktable :scope file :maxlevel 2 :block thismonth :step day > :stepskip0 t > > > > Daily report: [2019-11-01 Fri] > > | Headline | Time | > > |--+| > > | *Total time* | *1:00* | > > |--+| > > | Day 1| 1:00 | > > > > Daily report: [2019-11-02 Sat] > > | Headline | Time | > > |--+| > > | *Total time* | *2:00* | > > |--+| > > | Day 2| 2:00 | > > > > Daily report: [2019-11-03 Sun] > > | Headline | Time | > > |--+| > > | *Total time* | *3:00* | > > |--+| > > | Day 3| 3:00 | > > > > Daily report: [2019-11-03 Sun] > > | Headline | Time | > > |--+| > > | *Total time* | *4:00* | > > |--+| > > | Day 4| 4:00 | > > > > Daily report: [2019-11-04 Mon] > > | Headline | Time | > > |--+| > > | *Total time* | *5:00* | > > |--+| > > | Day 5| 5:00 | > > > > Daily report: [2019-11-05 Tue] > > | Headline | Time | > > |--+| > > | *Total time* | *6:00* | > > |--+| > > | Day 6| 6:00 | > > > > #+END: > > I can not reproduce this behavior. > > Could you please check again with emacs -Q? > > > Thanks. > > Hi, sorry I was not more clear - the issue occurs also with emacs -Q or with empty init.el on my system. Thanks
Re: Refresher on including R/ggplot2 output via latex/pdf?
> 2) why does this [still] work for Jack? (Jack, what's M-x org-version for > you?) This thread is old, but I finally realized why we were having discrepant results. It's because I was installing org-plus-contrib from org-mode ELPA via package.el, which pulls from "maint" branch. Since I've switched to pulling from git "master" branch, I've found that I need to specify ":results file" in order to get the link to the plot inserted.
org-mime-htmlize and signature
Hi, Although I prefer 80 column text mode for emails. But sometimes when you know that the mails are being read on smartphones then it is better to send additional part with html content so that the mail is rendered correctly on the mobile client. org-mime-htmlize helps in that. It converts the text in the message buffer into multipart message. But the conversion doesn't work well at the point of signature. In the text mode my signature is just my full-name separated from the email body using a double dash (--). After conversion the HTML part has signature and the separator on the same line; it doesn't insert an HTML line break before and after the separator (--). What is the solution/workaround for that? Regards -- Pankaj Jangid
Re: “Literate” python?
> On Nov 29, 2019, at 9:54 AM, Norman Walsh wrote:
>
> Hi,
>
> I’ve seen a couple of pointers recently to using Org mode and tangle
> to write more literate Emacs configurations. I use Org+babel all the
> time to write “interactive” documents, so I thought I’d try out tangle
> from Org.
>
> I didn’t want to start with something as comlicated as my Emacs
> config :-) so I figured I’d kick the tires with a small python
> program. That did not end well.
>
> Consider:
>
> #+TITLE: Python literate programming
> #+OPTIONS: html-postamble:nil
>
> It starts off as a completely standard Python3 program.
>
> ---%<--
> #+BEGIN_SRC python :tangle yes :weave no
> #!/usr/bin/env python3
>
> #+END_SRC
>
> It defines ~a~.
>
> #+BEGIN_SRC python :tangle yes
> def a():
>print("a")
>
>
> #+END_SRC
>
> And ~b~.
>
> #+BEGIN_SRC python :tangle yes
> def b():
>print("b")
>
>
> #+END_SRC
>
> Now ~c~ is a little more complicated:
>
> #+BEGIN_SRC python :tangle yes
> def c():
> print("c")
> #+END_SRC
>
> Not only does ~c~ print “c”, it calls ~a()~ and ~b()~.
>
> #+BEGIN_SRC python :tangle yes
> b()
> a()
> #+END_SRC
>
> Finally, make it importable. Not that you’d want to.
>
> #+BEGIN_SRC python :tangle yes
> if __name__ == "__main__":
>main()
> #+END_SRC
> --->%--
>
> That’s the script. It weaves into HTML more-or-less ok (there’s a
> weird black box at the front of indented lines, but I can come back to
> that later).
>
> It’s a complete mess when tangled.
>
> The extra blank lines between functions (to make pylint happy with
> some PEP guideline) have disappeared. I guess I could live with that,
> but the complete failure to preserve indention in the penultimate code
> block is a show stopper:
[results of tangling deleted]
A couple of things might help.
First, use the :noweb-ref argument to mark each of the code blocks you wish to
tangle.
Say `:noweb-ref tangleyes'. Or some more evocative name.
Remove the `:tangle yes' from each of those. Then, add a code block that has
only `<>' in it and tangle it.
#+begin_src python :noweb yes :tangle yes
<>
#+end_src
The remaining problem (as you will see) is the indentation. Fix this by adding
the `-i' flag to the penultimate code block, viz.
#+BEGIN_SRC python -i :noweb-ref tangleyes
b()
a()
#+END_SRC
See 12.6 Literal Examples and 15.10 Noweb Reference Syntax in the manual.
HTH,
Chuck
Re: is this a known issue in clocktable output?
Soubzriquet writes: > I'm new to using org-mode for time tracking, and have run into an odd issue > with using "day" steps where the date is getting offset sometimes. > > I saw the issue with 26.1, was not fixed by updating to current > environment with an empty init.el on OS X: [...] > * Day 1 > :LOGBOOK: > CLOCK: [2019-11-01 Fri 10:00]--[2019-11-01 Fri 11:00] => 1:00 > :END: > * Day 2 > :LOGBOOK: > CLOCK: [2019-11-02 Sat 10:00]--[2019-11-02 Sat 12:00] => 2:00 > :END: > * Day 3 > :LOGBOOK: > CLOCK: [2019-11-03 Sun 10:00]--[2019-11-03 Sun 13:00] => 3:00 > :END: > * Day 4 > :LOGBOOK: > CLOCK: [2019-11-04 Mon 10:00]--[2019-11-04 Mon 14:00] => 4:00 > :END: > * Day 5 > :LOGBOOK: > CLOCK: [2019-11-05 Tue 10:00]--[2019-11-05 Tue 15:00] => 5:00 > :END: > * Day 6 > :LOGBOOK: > CLOCK: [2019-11-06 Wed 10:00]--[2019-11-06 Wed 16:00] => 6:00 > :END: > > #+BEGIN: clocktable :scope file :maxlevel 2 :block thismonth :step day > :stepskip0 t > > Daily report: [2019-11-01 Fri] > | Headline | Time | > |--+| > | *Total time* | *1:00* | > |--+| > | Day 1| 1:00 | > > Daily report: [2019-11-02 Sat] > | Headline | Time | > |--+| > | *Total time* | *2:00* | > |--+| > | Day 2| 2:00 | > > Daily report: [2019-11-03 Sun] > | Headline | Time | > |--+| > | *Total time* | *3:00* | > |--+| > | Day 3| 3:00 | > > Daily report: [2019-11-03 Sun] > | Headline | Time | > |--+| > | *Total time* | *4:00* | > |--+| > | Day 4| 4:00 | > > Daily report: [2019-11-04 Mon] > | Headline | Time | > |--+| > | *Total time* | *5:00* | > |--+| > | Day 5| 5:00 | > > Daily report: [2019-11-05 Tue] > | Headline | Time | > |--+| > | *Total time* | *6:00* | > |--+| > | Day 6| 6:00 | > > #+END: I can not reproduce this behavior. Could you please check again with emacs -Q? Thanks.
