[O] switch export subtree
Hello, I'm looking for a way to switch of the export of a specific subtree in a document using a specific exporter. For example, let's assume the document * Section 1 ** Subsection 11 ** Subsection 12 I would like to export only Subsection 11 into HTML and only Subsection 12 into LATEX/PDF. Is there some kind of property to control that ? Or maybe another way ? Thanks a lot, Sébastien -- Save our in-boxes! http://emailcharter.org Dr. Sébastien Le Maguer Postdoctorate researcher Co-chair of SYNSIG (https://synsig.org/index.php/Main_Page) Saarland University Campus C7.4 - room 2.03 D-66123 Saarbrücken Germany phone : +49-681-302-70030 Mail: slemag...@coli.uni-saarland.de website : http://www.coli.uni-saarland.de/~slemaguer/
Re: [O] [PATCH] Add TITLE export to ox-md
Hello, Jay Kamat writes: > The markdown editor should support TITLE I'm not so sure about it. Vanilla Markdown does not support title. Neither does "ox-md.el" Is there any consensus about how title are handled in _vanilla_ syntax? > -(defun org-md-template (contents _info) > +(defun org-md-template (contents info) >"Return complete document string after Markdown conversion. > CONTENTS is the transcoded contents string. INFO is a plist used > as a communication channel." > - contents) > + (concat > +;; Generate title and subtitle, if possible > +(let ((title (and (plist-get info :with-title) > +(plist-get info :title))) > +(subtitle (plist-get info :subtitle)) > +(style (plist-get info :md-headline-style))) > + (when title > + (concat > + (org-md--headline-title style > + 1 (org-export-data title info)) > + (when subtitle > + (org-md--headline-title style > + 2 (org-export-data subtitle info)) > +contents)) But then you would need to shift all headlines 1 or 2 levels down. `setext' style becomes unusable because there is no room left for other headlines. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] Add TITLE export to ox-md
On Thu, Aug 24, 2017, 5:31 AM Nicolas Goaziou wrote: > > I'm not so sure about it. Vanilla Markdown does not support title. > Neither does "ox-md.el" > Correct, vanilla Markdown does not support title. The file name is the title. For example, the file names of the Wiki pages on GitHub are rendered as titles (that is again not using 100% vanilla Markdown, but that's a good example specific to this question about titles). Is there any consensus about how title are handled in _vanilla_ syntax? > > > -(defun org-md-template (contents _info) > > +(defun org-md-template (contents info) > >"Return complete document string after Markdown conversion. > > CONTENTS is the transcoded contents string. INFO is a plist used > > as a communication channel." > > - contents) > > + (concat > > +;; Generate title and subtitle, if possible > > +(let ((title (and (plist-get info :with-title) > > +(plist-get info :title))) > > +(subtitle (plist-get info :subtitle)) > > +(style (plist-get info :md-headline-style))) > > + (when title > > + (concat > > + (org-md--headline-title style > > + 1 (org-export-data title info)) > > + (when subtitle > > + (org-md--headline-title style > > + 2 (org-export-data subtitle info)) > > +contents)) > > But then you would need to shift all headlines 1 or 2 levels down. > `setext' style becomes unusable because there is no room left for other > headlines. I will soon submit ox-hugo for review for submission to Org. That is an enhanced Makrdown exporter backend, that also handles the post front matter generation for the Hugo static site generator. In there, I have added an option for the user to set an offset for the headings in a post. By default an Org heading with 1 star becomes level-1 heading in Markdown. For ox-hugo, I have set the default to an offset of 1. So the 1-star Org headings will now become level-2 headings in Markdown. Here's a little snippet that implements that: (let ((level-mark (make-string (+ loffset level) ?#))) (concat "\n" level-mark " " todo title " " anchor "\n\n")) (Full code: https://github.com/kaushalmodi/ox-hugo/blob/master/ox-hugo.el) While that doesn't translate title and subtitle to level 1 and level 2 Markdown headings, it at least helps keep the font sizes of title and level-1 Markdown headings different. I would suggest making the title/subtitle to Markdown headings optional at best. Because most HTML renderers will render the file name as title. So will end up with duplicate titles: the one rendered from file name and another from the level-1 Markdown heading based on the above quoted org-md-template snippet. @Jay Would this offset option help in ox-md? Maybe we eventually end up with 3 options (something like below): - org-md-title-as-h1 - org-md-subtitle-as-h2 - org-md-heading-offset WDYT? (Side question: Would it be preferred to create a scratch branch on Org for reviewing ox-hugo? Or would the GitHub repo mentioned above be fine?) -- Kaushal Modi
Re: [O] counter macro in dates?
On Wed, Aug 23, 2017, 9:46 PM Adam Porter wrote: > > That's very cool. Do you think Oleh would add it to Tiny? > Good question. I'll open an issue on that repo. When I wrote this, I wasn't too good with git, creating branches or submitting PR's. > -- Kaushal Modi
[O] is there an easier way to insert an internal link?
Der org-mode users, I'm in a big org-mode file and want to insert a link to a specific heading. Till now I go to that heading, do org-store-link, go back to the insert location and do org-insert-link. Isnt' there a way to say insert-internal-link-here, get a list of headings like refile targets, select one (optionally change link text) and be done? I do not want to move point in order to insert an internal link. I'm sure such facility already exists and I'm blind... Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-
[O] org export: how to avoid putting :export: in the exported file?
I often export org-files, most of the time to LaTeX/pdf, but the behaviour/problem is alike with many export filters. Let us say I want to export an org-file that runs like this: > * First Section > Some text > * Second Section :export: > Some more text > * Third Section > Even more text When I export this file to an ASCII buffer, the result is: > 1 Second Section:export: > > > Some more text (note «:export:» in the first line on the right) Likewise, in the case of a LaTeX export, the tag «export» is put in small caps in the exported file, with odt export in small caps and square brackets. Of course, it is easy to remove the tag in the output file. But I often export to pdf via LaTeX and automatically have deleted all intermediate files including the LaTeX file. So it would save me time to avoid putting the tag in the file in the first place. So, how can I avoid getting the «export» tag put in the output file? Thanks in advance, Rainer -- Prof. Dr. Rainer Thiel Institut für Altertumswissenschaften 07737 Jena, Germany (EU) r.th...@uni-jena.de
Re: [O] org export: how to avoid putting :export: in the exported file?
Hi Rainer, you could use: #+OPTIONS: tags:nil in you file. You can take a look at http://orgmode.org/manual/Export-settings.html to more options if you like. Cheers, LEslie On Thu, Aug 24, 2017 at 9:54 AM, Rainer Thiel wrote: > I often export org-files, most of the time to LaTeX/pdf, but the > behaviour/problem is alike with many export filters. > > Let us say I want to export an org-file that runs like this: > > > * First Section > > Some text > > * Second Section :export: > > Some more text > > * Third Section > > Even more text > > When I export this file to an ASCII buffer, the result is: > > > 1 Second Section:export: > > > > > > Some more text > > (note «:export:» in the first line on the right) > > Likewise, in the case of a LaTeX export, the tag «export» is put in > small caps in the exported file, with odt export in small caps and > square brackets. Of course, it is easy to remove the tag in the output > file. But I often export to pdf via LaTeX and automatically have > deleted all intermediate files including the LaTeX file. So it would > save me time to avoid putting the tag in the file in the first place. > > So, how can I avoid getting the «export» tag put in the output file? > > Thanks in advance, > > Rainer > -- > Prof. Dr. Rainer Thiel > Institut für Altertumswissenschaften > 07737 Jena, Germany (EU) > r.th...@uni-jena.de > > -- Leslie H. Watter
Re: [O] is there an easier way to insert an internal link?
I don't think this is in org-mode, but something like helm-org-in-buffer-headings has an action for doing something like that. John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu On Thu, Aug 24, 2017 at 4:23 AM, Gregor Zattler wrote: > Der org-mode users, > > I'm in a big org-mode file and want to insert a link to a > specific heading. > > Till now I go to that heading, do org-store-link, > go back to the insert location and do org-insert-link. > > Isnt' there a way to say insert-internal-link-here, > get a list of headings like refile targets, select one > (optionally change link text) and be done? > > I do not want to move point in order to insert an > internal link. > > > I'm sure such facility already exists and I'm blind... > > Ciao, Gregor > -- > -... --- .-. . -.. ..--.. ...-.- > > >
[O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours
Hi,
I may have found a bug in the sorting of clocktables.
I am summing up clocked time over time periods.
As long as the clocksum is under "100:00" (6 characters including ":") sorting
seems to be ok:
#+BEGIN: clocktable :maxlevel 1 :properties ("CATEGORY") :fileskip0 t :scope agenda-with-archives :tstart "<2017-01-01 So 00:00>" :tend
"<2017-01-20 Fr 00:00>" :sort (4 . ?T)
#+CAPTION: Clock summary at [2017-08-24 Do 15:04]
| File | CATEGORY| Headline |Time |
|---+-+--+-|
| | ALL | *Total time* | *97:30* |
|---+-+--+-|
| Projectmanagement.org | | *File time* | *96:45* |
| | annonymised | annonymised | 24:45 |
| | annonymised | annonymised | 17:45 |
| | annonymised | annonymised | 10:45 |
| | annonymised | annonymised |8:00 |
| | annonymised | annonymised |7:45 |
| | annonymised | annonymised |5:00 |
| | annonymised | annonymised |4:00 |
| | annonymised | annonymised |3:45 |
| | annonymised | annonymised |2:00 |
| | annonymised | annonymised |2:00 |
| | annonymised | annonymised |1:45 |
| | annonymised | annonymised |1:45 |
| | annonymised | annonymised |1:15 |
| | annonymised | annonymised |0:45 |
| | annonymised | annonymised |0:45 |
| | annonymised | annonymised |0:30 |
| | annonymised | annonymised |0:30 |
| | annonymised | annonymised |0:30 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
| | annonymised | annonymised |0:15 |
|---+-+--+-|
| FILE2.org | | *File time* | *0:45* |
| | annonymised | annonymised |0:45 |
#+END:
As soon as the sum grows higher than 100:00 sorting is corrupted:
#+BEGIN: clocktable :maxlevel 1 :properties ("CATEGORY") :fileskip0 t :scope agenda-with-archives :tstart "<2017-01-01 So 00:00>" :tend
"<2017-01-23 Mo 00:00>" :sort (4 . ?T)
#+CAPTION: Clock summary at [2017-08-24 Do 16:14]
| File | CATEGORY| Headline | Time |
|---+-+--+--|
| | ALL | *Total time* | *104:45* |
|---+-+--+--|
| | annonymised | annonymised |28:00 |
| | annonymised | annonymised |18:45 |
| | annonymised | annonymised |10:45 |
| | annonymised | annonymised | 8:00 |
| | annonymised | annonymised | 8:00 |
| | annonymised | annonymised | 7:15 |
| Projectmanagement.org | | *File time* | *104:00* |
| | annonymised | annonymised | 4:00 |
| | annonymised | annonymised | 3:45 |
| | annonymised | annonymised | 2:00 |
| | annonymised | annonymised | 2:00 |
| | annonymised | annonymised | 1:45 |
| | annonymised | annonymised | 1:45 |
| | annonymised | annonymised | 1:15 |
| | annonymised | annonymised | 0:45 |
| | annonymised | annonymised | 0:45 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
|
Re: [O] [PATCH] Add TITLE export to ox-md
> I'm not so sure about it. Vanilla Markdown does not support title. > Neither does "ox-md.el" I agree that vanilla markdown does not support title, but if ox-md does not support any form of title, then there is disparity between the output of other org exports and the markdown exporter. I would like to solve that disparity if possible. > Correct, vanilla Markdown does not support title. The file name is the title. I'm not entirely sure about that (file name being the title). Unfortunately markdown is very fragmented, so it's hard to tell what the 'standard' is. From the markdown that I've worked with, this isn't the case. The original markdown tool (https://daringfireball.net/projects/markdown/) dosen't seem to output filename titles in it's export, so I wouldn't think it's part of the vanilla standard. > But then you would need to shift all headlines 1 or 2 levels down. > `setext' style becomes unusable because there is no room left for other > headlines. Is there a reason we need to move all the other header under the title header? I was thinking of leaving the rest of the headlines as they are. So: #+TITLE: My Title * One ** Two Would export to # My Title # One ## Two It's a little bit ugly to have two h1 headings right next to each other, though. Another option is to take advantage of html features of markdown to format the title in a way that does not alter the headings (similar to how the TOC is exported now). For example, we could add My Title to the start of the markdown, but that seems to break the github markdown renderer. Does anyone who knows more html have any ideas here (besides adding h1 headings in html)? I don't like the idea of shifting headlines down a level to accommodate the title since people would then be unable to create new H1 headings in markdown files with a title. > Maybe we eventually end up with 3 options (something like below): > > - org-md-title-as-h1 > - org-md-subtitle-as-h2 > - org-md-heading-offset that's probably the best idea I've heard so far, since I would imagine most people would either not want to have two H1 headings right after each other, or not want to have their headings shifted. Having such options would allow people to pick the scenario they want (shifting headings under the title, including the title but no offset, or not including the title at all). Does creating these options (defaulting to nil) sound like a good plan to move forward on? Other ideas and feedback would be appreciated, (since this is a tricky situation, standards wise). -Jay PS: ox-hugo looks very nice, and I look forward to trying it out! :)
Re: [O] counter macro in dates?
On Wed, Aug 23, 2017 at 9:46 PM Adam Porter wrote: > > That's very cool. Do you think Oleh would add it to Tiny? > PR submitted :) https://github.com/abo-abo/tiny/pull/9 -- Kaushal Modi
[O] Conditional summing in column-mode?
I have the following column-mode defined in =~/org/Holidays.org=:
#+BEGIN_SRC org
,#+COLUMNS: %TIMESTAMP(When) %ITEM(What) %CONFIRMED(Confirmed?){X/}
%DAYS(Days){+}
,#+Confirmed_ALL: "[ ]" "[X]"
,#+TODO: TODO | DONE CANCELLED
#+END_SRC
Is it possible to have the =%DAYS(Days){+}= part only sum up rows that
have an =[X]= in their =Confirmed?= property?
Stig
--
; GNU Emacs 26.0.50, Org mode version 9.0.9
Re: [O] switch export subtree
> On Aug 24, 2017, at 12:12 AM, Sébastien Le Maguer
> wrote:
>
> Hello,
>
> I'm looking for a way to switch of the export of a specific subtree in a
> document using a specific exporter. For example, let's assume the document
>
> * Section 1
> ** Subsection 11
> ** Subsection 12
>
> I would like to export only Subsection 11 into HTML and only Subsection 12
> into LATEX/PDF.
>
> Is there some kind of property to control that ? Or maybe another way ?
You want to use tags.
See
(info "(org) Tags")
(info "(org) Export settings")
Something like this should do it. Other backends will include both.
#+BEGIN_SRC emacs-lisp :exports results :results value
(setq org-export-select-tags
(case org-export-current-backend
('latex '("latex"))
('html '("html"
#+END_SRC
* abc :latex:
hi this is latex
* def :html:
hi this is html
HTH,
Chuck
Re: [O] org-protocol: deal with broken links on windows
Hi Nikolay, Thanks for your reply. I checked a few things today: I am using Org mode version 9.0.9 (9.0.9-82-gb862c2-elpaplus, org-plus-contrib-20170814/) and the unofficial emacs build GNU Emacs 25.2.1 (x86_64-w64-mingw32) of 2017-04-24 from http://sourceforge.net/projects/emacsbinw64/ (supposedly straight from original sources). > emacsclientw.exe > "org-protocol:/capture?template=w&url=http%3A%2F%2Fjira%2Fbrowse%2FSDST-705&title=SOMETHING&body=" 1) Without any patch/advice, calling emacsclientw directly on this address (modulo template letter) works fine, as does a call with the full executable path. I think the path prefix is weird, but fine with me. The culprit (independent of the prefix) is the "/" before the query string. So thanks for narrowing this down, first of all. 2) Just a side note: store-link (instead of capture) shows the exact same behavior. 3) Here are the bookmarklets I use... >--< javascript:location.href='org-protocol://store-link?url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title)+'&body='+encodeURIComponent(window.getSelection()) javascript:location.href='org-protocol://capture?template=y&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title)+'&body='+encodeURIComponent(window.getSelection()) >--< 4) ...and the registry entries >--< REGEDIT4 [HKEY_CLASSES_ROOT\org-protocol] @="URL:org-protocol" "URL Protocol"="" [HKEY_CLASSES_ROOT\org-protocol\shell] [HKEY_CLASSES_ROOT\org-protocol\shell\open] [HKEY_CLASSES_ROOT\org-protocol\shell\open\command] @="\"C:\\Program Files\\Emacs\\bin\\emacsclientw.exe\" --no-wait \"%1\"" >--< I think this is all as it should be, and I have tried to make the minimal changes to get a working system. 5) Soo the remaining puzzle: How can the "/" get in there? As I said, it happens when called from both FF (although I have not used that for a few weeks now) and Iridium. It seems to happen somewhere b/w the browser and emacsclientw, ie, in the Windows "protocol" handling, I suppose? If other people can confirm (or even explain) this behavior, we could decide if there should be a transformation on the FNAME argument. In that case, it should definitely leave the leading executable path alone. Thanks a lot so far! Ingo
[O] Bug: org-copy-visible includes emphasis markerse hidden by org-hide-emphasis-markers [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)]
Emacs : GNU Emacs 25.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.16) of 2017-07-15 Package: Org-mode version 8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/) With evil-mode enabled (bug still applies without using evil, see: https://github.com/emacs-evil/evil/issues/907), start Emacs, evaluate (setq org-hide-emphasis-markers t). Open a org file containing the following line: ~$ firejail --get= ~ which is shown in the visible buffer as: $ firejail --get= Then, visually select via v from the first character "$" to the last character ">" of the line. What's copied into the clipboard is (note the "~" in the beginning): ~$ firejail --get= instead of: $ firejail --get= Also, copying the entire line with V via org-copy-visible will yield ~$ firejail --get= ~. I only use Emacs with evil-mode enabled, so I'm not sure what Emacs equivalents are, but it has the same issue even without using evil according to the evil developer (see github issue posted above).
[O] LaTeX > PDF blocked by extender chars in filename
Dear all. I hope this is the right place to share this. If not, please forgive me for the bothering and point me to the right place. When a referenced file has an extended character in it's filename, the export to pdf function ends without export nor any informative error. I found it by chance... I do most of my work in spanish but I tend not to use spaces or extended chars (á, é, í, ó, ú, ñ at least) in filenames to simplify potential issues with the OS. However, today a "ñ" slipped by and suddently I couldn't export the document to pdf. I found no other information in the messages buffer than buffername".pdf wasn't produced". It took me some time to bisect the origin and finally got it. The file > img/ProcesoDeDiseñoDeInteraccion.pdf was translated/inserted on the org buffer as > img/ProcesoDeDise%C3%B1oDeInteraccion.pdf Is this how it's supposed to be? Some relevant info: + OS: Debian 8.9 + Emacs: GNU Emacs 24.5.1 of 2016-03-19 on trouble, modified by Debian + Org-mode: Org-mode version 8.3.4 (8.3.4-88-g792bb9-elpaplus) locale says: --8<---cut here---start->8--- LANG=es_AR.UTF-8 LANGUAGE=es_AR:es LC_CTYPE="es_AR.UTF-8" LC_NUMERIC="es_AR.UTF-8" LC_TIME="es_AR.UTF-8" LC_COLLATE="es_AR.UTF-8" LC_MONETARY="es_AR.UTF-8" LC_MESSAGES="es_AR.UTF-8" LC_PAPER="es_AR.UTF-8" LC_NAME="es_AR.UTF-8" LC_ADDRESS="es_AR.UTF-8" LC_TELEPHONE="es_AR.UTF-8" LC_MEASUREMENT="es_AR.UTF-8" LC_IDENTIFICATION="es_AR.UTF-8" LC_ALL= --8<---cut here---end--->8--- Is it any other test or info that could be useful? I'd be glad to help. Thanks a lot, as always, for such a worderful tool and community. :) Best... -- eduardo mercovich Donde se cruzan tus talentos con las necesidades del mundo, ahí está tu vocación. (Anónimo)
Re: [O] is there an easier way to insert an internal link?
Hi John, org-moders, * John Kitchin [2017-08-24; 06:41]: > I don't think this is in org-mode, but something like > helm-org-in-buffer-headings has an action for doing something like that. Yupp, it's on "C-c l" and asks for the description. Thanks a lot, Gregor
Re: [O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours
Hello,
Rainer Stengele writes:
> I may have found a bug in the sorting of clocktables.
> I am summing up clocked time over time periods.
[...]
> As soon as the sum grows higher than 100:00 sorting is corrupted:
>
> #+BEGIN: clocktable :maxlevel 1 :properties ("CATEGORY") :fileskip0 t :scope
> agenda-with-archives :tstart "<2017-01-01 So 00:00>" :tend
> "<2017-01-23 Mo 00:00>" :sort (4 . ?T)
>
> #+CAPTION: Clock summary at [2017-08-24 Do 16:14]
> | File | CATEGORY| Headline | Time |
>
> |---+-+--+--|
> | | ALL | *Total time* | *104:45* |
> |---+-+--+--|
> | | annonymised | annonymised |28:00 |
> | | annonymised | annonymised |18:45 |
> | | annonymised | annonymised |10:45 |
> | | annonymised | annonymised | 8:00 |
> | | annonymised | annonymised | 8:00 |
> | | annonymised | annonymised | 7:15 |
> | Projectmanagement.org | | *File time* | *104:00* |
> | | annonymised | annonymised | 4:00 |
> | | annonymised | annonymised | 3:45 |
> | | annonymised | annonymised | 2:00 |
> | | annonymised | annonymised | 2:00 |
> | | annonymised | annonymised | 1:45 |
> | | annonymised | annonymised | 1:45 |
> | | annonymised | annonymised | 1:15 |
> | | annonymised | annonymised | 0:45 |
> | | annonymised | annonymised | 0:45 |
> | | annonymised | annonymised | 0:30 |
> | | annonymised | annonymised | 0:30 |
> | | annonymised | annonymised | 0:30 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> | | annonymised | annonymised | 0:15 |
> |---+-+--+--|
> | FILE2.org | | *File time* | *0:45* |
> | | annonymised | annonymised | 0:45 |
> #+END:
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours
Am 25.08.2017 um 00:07 schrieb Nicolas Goaziou:
Hello,
Rainer Stengele writes:
I may have found a bug in the sorting of clocktables.
I am summing up clocked time over time periods.
[...]
As soon as the sum grows higher than 100:00 sorting is corrupted:
#+BEGIN: clocktable :maxlevel 1 :properties ("CATEGORY") :fileskip0 t :scope
agenda-with-archives :tstart "<2017-01-01 So 00:00>" :tend
"<2017-01-23 Mo 00:00>" :sort (4 . ?T)
#+CAPTION: Clock summary at [2017-08-24 Do 16:14]
| File | CATEGORY| Headline | Time |
|---+-+--+--|
| | ALL | *Total time* | *104:45* |
|---+-+--+--|
| | annonymised | annonymised |28:00 |
| | annonymised | annonymised |18:45 |
| | annonymised | annonymised |10:45 |
| | annonymised | annonymised | 8:00 |
| | annonymised | annonymised | 8:00 |
| | annonymised | annonymised | 7:15 |
| Projectmanagement.org | | *File time* | *104:00* |
| | annonymised | annonymised | 4:00 |
| | annonymised | annonymised | 3:45 |
| | annonymised | annonymised | 2:00 |
| | annonymised | annonymised | 2:00 |
| | annonymised | annonymised | 1:45 |
| | annonymised | annonymised | 1:45 |
| | annonymised | annonymised | 1:15 |
| | annonymised | annonymised | 0:45 |
| | annonymised | annonymised | 0:45 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:30 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
| | annonymised | annonymised | 0:15 |
|---+-+--+--|
| FILE2.org | | *File time* | *0:45* |
| | annonymised | annonymised | 0:45 |
#+END:
Fixed. Thank you.
Regards,
Works, thanks very much!
Regards,
Rainer
