Re: [O] [PATCH] org-mobile.el: Skip after and before elements
Viktor Rosenfeld writes: TINYCHANGE Just declaring things TINYCHANGE doesn't magically make it so, please remember that the limit is cumulative. Org already has changes from you to core files. Additionally you weren't listed as a TINYCHANGE contributor on Worg (I have just added you). Please read http://orgmode.org/worg/org-contribute.html Make up your mind about assigning copyright to the FSF and let us know the outcome. Thank you. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Hello, Viktor Rosenfeld listuse...@gmail.com writes: * ox-icalendar.el (org-icalendar-entry): Honor setting of `org-icalendar-with-timestamps' for timestamps on headlines and checkboxes. The setting `org-icalendar-with-timestamps' was only applied to timestamps which do not appear on a heading or on a checkbox. E.g., with `org-icalendar-with-timestamps' set to 'active, an heading containing an inactive timestamp on would be exported. This patch fixes this. This would make icalendar back-end inconsistent with other back-ends, see `org-export-with-timestamps' docstring. If inconsistency is desirable in this case, `org-icalendar-with-timestamps' docstring should clearly state it. Regards, -- Nicolas Goaziou
[O] Indicate programming language on babel export to markdown.
GitHub support programming language highlight for markdown: ```lisp (some-code) ``` When I use org-md-export-to-markdown for such org snippet #+begin_src emacs-lisp (some-code) #+end_src babel is not indicate `emacs-lisp` in the resulting markdown file. Is it possible? How to achieve that? -- Kostafey kosta...@gmail.com
Re: [O] Indicate programming language on babel export to markdown.
Hello, Konstantin kosta...@gmail.com writes: GitHub support programming language highlight for markdown: ```lisp (some-code) ``` When I use org-md-export-to-markdown for such org snippet #+begin_src emacs-lisp (some-code) #+end_src babel is not indicate `emacs-lisp` in the resulting markdown file. Org provides vanilla Markdown syntax only. Is it possible? How to achieve that? You need to create a derived back-end which will support github flavoured markdown syntax. See section 12.13 in Org manual. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Hi Nicolas, Nicolas Goaziou wrote: Hello, Viktor Rosenfeld listuse...@gmail.com writes: * ox-icalendar.el (org-icalendar-entry): Honor setting of `org-icalendar-with-timestamps' for timestamps on headlines and checkboxes. The setting `org-icalendar-with-timestamps' was only applied to timestamps which do not appear on a heading or on a checkbox. E.g., with `org-icalendar-with-timestamps' set to 'active, an heading containing an inactive timestamp on would be exported. This patch fixes this. This would make icalendar back-end inconsistent with other back-ends, see `org-export-with-timestamps' docstring. If inconsistency is desirable in this case, `org-icalendar-with-timestamps' docstring should clearly state it. The docstring of `org-icalendar-with-timestamps' already states: This variable has precedence over `org-export-with-timestamps'. It can also be set with the #+OPTIONS line, e.g. :t. I believe that inconsistency is desirable here. Consider the following use case with three headlines: * TODO An appointment in the future 2013-08-12 So 09:00 * DONE A note about an appointment in the past [2013-08-10 Fr 09:00] * WAIT A reminder how long I've been waiting for something [2013-08-10 Fr] The previous behavior, with `org-icalendar-with-timestamps' set to 'active, was that the first and the last headlines were picked up (even though the timestamp in the last headline is inactive). This was unexpected because the two inactive timestamps are handled differently. My expectation was that only the first headline should have been exported. This is what my patch achieves. (Putting timestamps on the heading is useful to me because then I can see them in the agenda. Also, I often put timestamps on lines with checkboxes. However, I do not want to see any of those in my calendar when I export only active timestamps.) Cheers, Viktor Regards, -- Nicolas Goaziou
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Hi Aaron, Aaron Ecay wrote: (lambda (ts) - (let ((uid (format TS%d-%s (incf counter) uid))) -(org-icalendar--vevent entry ts uid summary loc desc cat))) + (let ((type (org-element-property :type ts)) + (uid (format TS%d-%s (incf counter) uid))) +(when (or (eq with-timestamps 'all) Here, I think you want to compare with t, not 'all (check the defcustom for ‘org-icalendar-with-timestamps’). Thanks, fixed! +(and (eq with-timestamps 'active) + (or (eq type 'active) + (eq type 'active-range))) This is only a cosmetic comment, so feel free to disregard it, but: might the ‘(or ...)’ be cleaner as ‘(memq type '(active active-range))’? Thanks, fixed! I did not like the construction with `or' but I didn't know about `memq'. Learning Elisp as I go... New patch is attached. Cheers, Viktor -- Aaron Ecay From 52511b5e2a538d3bb0375c2e32caef0a27e1998e Mon Sep 17 00:00:00 2001 From: Viktor Rosenfeld listuse...@gmail.com Date: Sun, 11 Aug 2013 03:59:29 +0200 Subject: [PATCH] ox-icalendar: fix handling of timestamps * ox-icalendar.el (org-icalendar-entry): Honor setting of `org-icalendar-with-timestamps' for timestamps on headlines and checkboxes. The setting `org-icalendar-with-timestamps' was only applied to timestamps which do not appear on a heading or on a checkbox. E.g., with `org-icalendar-with-timestamps' set to 'active, an heading containing an inactive timestamp on would be exported. This patch fixes this. TINYCHANGE --- lisp/ox-icalendar.el | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/lisp/ox-icalendar.el b/lisp/ox-icalendar.el index c6ab295..ab83a48 100644 --- a/lisp/ox-icalendar.el +++ b/lisp/ox-icalendar.el @@ -580,15 +580,22 @@ inlinetask within the section. ;; When collecting plain timestamps from a headline and ;; its title, skip inlinetasks since collection will ;; happen once ENTRY is one of them. - (let ((counter 0)) + (let ((counter 0) + (with-timestamps (plist-get info :with-timestamps))) (mapconcat 'identity (org-element-map (cons (org-element-property :title entry) (org-element-contents inside)) 'timestamp (lambda (ts) - (let ((uid (format TS%d-%s (incf counter) uid))) -(org-icalendar--vevent entry ts uid summary loc desc cat))) + (let ((type (org-element-property :type ts)) +(uid (format TS%d-%s (incf counter) uid))) +(when (or (eq with-timestamps t) + (and (eq with-timestamps 'active) + (memq type '(active active-range))) + (and (eq with-timestamps 'inactive) + (memq type '(inactive 'inactive-range + (org-icalendar--vevent entry ts uid summary loc desc cat info nil (and (eq type 'headline) 'inlinetask)) )) ;; Task: First check if it is appropriate to export it. -- 1.8.3.4
Re: [O] [PATCH] org-mobile.el: Skip after and before elements
Hi Achim, Achim Gratz wrote: Viktor Rosenfeld writes: TINYCHANGE Just declaring things TINYCHANGE doesn't magically make it so, please remember that the limit is cumulative. Org already has changes from you to core files. Additionally you weren't listed as a TINYCHANGE contributor on Worg (I have just added you). Please read http://orgmode.org/worg/org-contribute.html Make up your mind about assigning copyright to the FSF and let us know the outcome. Thank you. Point taken. I did not know that the limit was cumulative. I've started the copyright assignment process and am waiting for the form to arrive. Cheers, Viktor Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Viktor Rosenfeld listuse...@gmail.com writes: The docstring of `org-icalendar-with-timestamps' already states: This variable has precedence over `org-export-with-timestamps'. It can also be set with the #+OPTIONS line, e.g. :t. This wouldn't be sufficient: has precedence over isn't a synonym for change the meaning of. I believe that inconsistency is desirable here. Consider the following use case with three headlines: * TODO An appointment in the future 2013-08-12 So 09:00 * DONE A note about an appointment in the past [2013-08-10 Fr 09:00] * WAIT A reminder how long I've been waiting for something [2013-08-10 Fr] The previous behavior, with `org-icalendar-with-timestamps' set to 'active, was that the first and the last headlines were picked up (even though the timestamp in the last headline is inactive). This was unexpected because the two inactive timestamps are handled differently. This is to be expected according to `org-export-with-timestamps'. My expectation was that only the first headline should have been exported. This is what my patch achieves. The meaning of `org-export-with-timestamps' is the result of a discussion in this ML. Please read the whole thread starting at: http://permalink.gmane.org/gmane.emacs.orgmode/69971 Regards, -- Nicolas Goaziou
[O] odt export version conflict on emacs for mac os x
The version of org that comes with my stock Emacs on OS X (from emacsformacosx.org) seems to conflict with my git installation of org. This is particularly evident when trying to use ODT export. Emacs.app is located in the usual /Applications folder. The newer org, which I intend to completely supplant the version that comes with Emacs, was installed with prefix /usr/local/share using the 'make up2' command. My minimal init file is: (setq load-path (cons /usr/local/share/emacs/site-lisp/org load-path)) I start Emacs from the command line: /Applications/Emacs.app/Contents/MacOS/Emacs -Q -l ~/.emacs.d/minimalinit.el ~/test.org Doing M-x org-version yields: Org-mode version 8.0.7 (release_8.0.7-369-g9154c7 @ /usr/local/share/emacs/site-lisp/org/) I immediately browse the ODT customization options showing that all variables are prefixed with org-export-odt-. In order to be able to select ODT in the export dispatcher, I have to add odt to org-export-backends. Curiously, it shows that it is changed outside of customize before I make any changes. So I have to unselect odt and reselect it and then Save for Current Session for ODT export to be enabled. When I finally use the dispatcher to generate an ODT file, the following happens: 1) an odt file is generated (good) 2) These Emacs messages appear (bad): Debug (ox-odt): Searching for OpenDocument styles files... Debug (ox-odt): Trying /usr/share/emacs/etc/org/styles/... [2 times] Debug (ox-odt): Trying /usr/local/share/emacs/etc/styles/... Debug (ox-odt): Trying /usr/local/share/emacs/site-lisp/org/etc/styles/... Debug (ox-odt): Trying /Applications/Emacs.app/Contents/Resources/etc/org/... Debug (ox-odt): Using styles under /Applications/Emacs.app/Contents/Resources/etc/org/ Debug (ox-odt): Searching for OpenDocument schema files... Debug (ox-odt): Trying /usr/share/emacs/etc/org/schema/... [2 times] Debug (ox-odt): No OpenDocument schema files installed 3) I find that there are new variables with the org-odt- prefix. Many of them seem like duplicates of the org-export-odt set (bad). It appears that the old version of ODT export (the one bundled inside Emacs.app) is getting loaded and ox-odt is looking in the wrong directories for schemas and styles. Explicitly setting org-export-backends, org-export-odt-schema-dir, and org-export-odt-styles-file in minimalinit.el has no effect. These variables seem to be superseded when ox-odt is invoked. I started digging into this when I noticed some odd behavior while using ODT export. I think I am stuck using the older, buggier ox-odt and my setup is mixing two versions of org. I have installed the latest release of Emacs for Mac OS X: GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2013-03-13 on bob.porkrind.org
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Hi Nicolas, Nicolas Goaziou wrote: Viktor Rosenfeld listuse...@gmail.com writes: The docstring of `org-icalendar-with-timestamps' already states: This variable has precedence over `org-export-with-timestamps'. It can also be set with the #+OPTIONS line, e.g. :t. This wouldn't be sufficient: has precedence over isn't a synonym for change the meaning of. Okay, I see the change in meaning now. I believe that inconsistency is desirable here. Consider the following use case with three headlines: * TODO An appointment in the future 2013-08-12 So 09:00 * DONE A note about an appointment in the past [2013-08-10 Fr 09:00] * WAIT A reminder how long I've been waiting for something [2013-08-10 Fr] The previous behavior, with `org-icalendar-with-timestamps' set to 'active, was that the first and the last headlines were picked up (even though the timestamp in the last headline is inactive). This was unexpected because the two inactive timestamps are handled differently. This is to be expected according to `org-export-with-timestamps'. My expectation was that only the first headline should have been exported. This is what my patch achieves. The meaning of `org-export-with-timestamps' is the result of a discussion in this ML. Please read the whole thread starting at: http://permalink.gmane.org/gmane.emacs.orgmode/69971 Thanks for the link. (It made me realize that something was wrong in my setup. For some reason, I was picking up `org-export-with-timestamps' from `org-exp.el', i.e., pre-8.0 code.) In any case, the docstring of `org-export-with-timestamps' states: This only applies to timestamps isolated in a paragraph containing only timestamps. Other timestamps are always exported. This explains the observerd behavior. But I don't think it's appropriate for the export to iCal. Quoting Carsten from http://thread.gmane.org/gmane.emacs.orgmode/69971/focus=70068: Some people throw in time stamps often while they work, just as a little label, indicating that they were working on this at a specific date, or that the entry was created on a specific date. Many people I know have a hook that throws in such a time stamp in each new entry created. This creates a lot of clutter when you print it, which is why you can turn off export of timestamps. That option was not meant for a contextual line like your first example. If you use the time stamps in this way, you probably will not turn off timestamp export at all, you will just leave it on. If you mix both ways of using time stamps - well, too bad. So the timestamp in the following example is clutter and can be turned off (i.e., it will not be exported): * Meet X 2013-08-11 So But the following will always be exported, even though the date is just o note and will not not cause the task to appear in the agenda: * Do stuff - Started on [2013-08-11 So] I want to make the iCal export mirror the agenda. I think the underlying problem is that there is no way in Org to annotate a timestamp as a fixed appointment. There's SCHEDULED and DEADLINE, but there's no APPT. The consensus is to use a standalone active timestamp for fixed appointments, which is easy enough. But then I would expect only those to appear in an iCal export. So I propose to append the docstring of `org-icalendar-export-timestamps': This variable has precedence over and overrides the behavior of `org-export-with-timestamps'. The setting is applied to every timestamp below a headline and not only to those which are isolated in a paragraph containing only timestamps. It can also be set with the #+OPTIONS line, e.g. :t. Cheers, Viktor (PS: Sorry for the long post.) Regards, -- Nicolas Goaziou
Re: [O] [PATCH] ox-icalendar: fix handling of timestamps
Hi Nicolas, Viktor Rosenfeld wrote: So I propose to append the docstring of `org-icalendar-export-timestamps': This variable has precedence over and overrides the behavior of `org-export-with-timestamps'. The setting is applied to every timestamp below a headline and not only to those which are isolated in a paragraph containing only timestamps. It can also be set with the #+OPTIONS line, e.g. :t. I just realized that this is not enough. The option `org-icalendar-with-timestamps' already changes the meaning of `org-export-with-timestamps'. The latter only removes timestamps from the export whereas during the iCalendar export the presence of a timestamp determines whether the heading is exported at all. So it's more akin to the behavior of :export: and :noexport: tags. I would change the docstring of `org-icalendar-export-timestamps' as such: Non-nil means export headlines with timestamps. It can be set to any of the following values: t export headlines containing any kind of timestamp `active'export headlines containing active timestamps `inactive' export headlines containing inactive timestamps nil do not any headlines Note: This variable overrides the behavior of `org-export-with-timestamps'. `org-export-with-timestamps' controls whether a timestamp is exported or removed from the export. `org-icalendar-export-timestamps' controls whether a headline is exported or removed from the exported. In addition, `org-icalendar-export-timestamps' applies to every timestamp below a headline and not only to those which are isolated in a paragraph containing only timestamps. This variable can also be set with the #+OPTIONS line, e.g. :t. Note that setting the variable in the OPTIONS line is useful to remove a file from the iCalendar export even though it is displayed in the agenda. I actually have this usecase (although right now I exclude by tag). Cheers, Viktor
[O] org package file proposition
Hello, I'm currently working on my spare time on a little CMS build around org mode. The aim of this little project is to provide an easy way to maintain a customizable personal Website, where content are provided by org file. As I was looking for a way to easily publish sort of blog post written in orgmode, with pictures in it, I came to the idea of standard way to package both org file and all other things it depends on. So, I would like to present you my idea for an orgx file format. I've written some specification here: http://etienne.depar.is/resource/orgx.html and a first implementation with this bash script: http://projects.depar.is/0xGA/doc/tip/usr/bin/orgx (warning, it depends on an emacs init file a put here: http://projects.depar.is/0xGA/doc/tip/etc/batch.el). To create an orgx file, you just have to call this script without any argument (./orgx for example). After this, to edit an orgx file, you just have to pass it as a parameter (./orgx myfile.orgx for example). And to export this orgx file to odt, pdf or tex, you have to use the following command for example: ./orgx myfile.orgx export -o odt -l path/to/batch.el As explain in the puposed specs, orgx file are just zip file, so if you have created one and want to inspect its content, just unzip it. I've search a bit before writing these specs, so I hope I don't have miss similar work. I'm really open to all comments to improve this proposition. Thus, don't hesitate to try it and let me know your impressions. Thank you very much in advance for your support. -- Étienne Deparis http://etienne.depar.is/ twitter: @milouse xmpp: milo...@jabber.fr 06 76 28 00 58
[O] example blocks remove initial whitespace
#+BEGIN_EXAMPLE PR /\ #+END_EXAMPLE pre class=example PR /\ /pre This must be deliberate, but I don't know how to disable that feature. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] narrowing bug when inserting a headline
On 8/8/13, Carsten Dominik carsten.domi...@gmail.com wrote: On 30.7.2013, at 20:30, Samuel Wales samolog...@gmail.com wrote: I think this is now fixed. Confirmed. Thanks, Carsten. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
[O] ODT export
I have an org file with some latex src code blocks embedded in it. These are mainly tables which could not be made using orgmode and had to be coded in latex (orgmode does not allow putting notes at the bottom of table using something like threeparttable). I now need to convert the document to odt. What is my best bet? How can I convert latex src code blocks to native org syntax, even if it means loosing some of the things (for example, the threeparttable stuff). Or do I need to write it all over again? Vikas
Re: [O] ODT export
Hello Vikas, I don't think you can convert latex bits to org automatically. I was in a similar situation few days ago. I had very satisfying results using LaTeX2HTML and libreoffice convert. (org → latex → html → odt/doc) Citing the procedure I used to convert. ╭─┤ http://askubuntu.com/a/239332/18411 ├─ │Believe it or not, with complex documents and lots of packages included, I got │much better results with LaTeX2HTML than with LaTeX2RTF, Pandoc or TeX4ht. │ │ latex2html texfile.tex -split 0 -no_navigation -info -address -html_version 4.0,unicode │ │This will generate a folder with the same texfile name, so you'll be able to │convert the generated HTML to ODT: │ │libreoffice --headless --convert-to odt:OpenDocument Text Flat XML texfile/index.html │ │This will produce a index.odt file. Take a look at this answer to check how to │use LibreOffice's convert filters. ╰─ On Aug 12 2013, Vikas Rawal vikasli...@agrarianresearch.org wrote: I have an org file with some latex src code blocks embedded in it. These are mainly tables which could not be made using orgmode and had to be coded in latex (orgmode does not allow putting notes at the bottom of table using something like threeparttable). I now need to convert the document to odt. What is my best bet? How can I convert latex src code blocks to native org syntax, even if it means loosing some of the things (for example, the threeparttable stuff). Or do I need to write it all over again? Vikas Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
[O] orgmode.org is missing a link to the split HTML manual
Is there a reason why the org-manual's index is not linked from the head orgmode.org page? Under orgmode.org/#docs, the link to the HTML manual is http://orgmode.org/org.html, which downloads the entire contents of the manual into the browser. This is perhaps tolerable on a full-size computer, but if I want to check something using the browser on my tablet, the huge/immense/massive page grinds my tablet to a halt. This index works beautifully, though: http://orgmode.org/manual/index.html I think it might be helpful if the main org page gave users the choice whether they want to download the whole manual as one page, or browse separate pages for the various sections and subsections. hjh
Re: [O] orgmode.org is missing a link to the split HTML manual
On 12.8.2013, at 05:37, James Harkins jamshar...@gmail.com wrote: Is there a reason why the org-manual's index is not linked from the head orgmode.org page? Under orgmode.org/#docs, the link to the HTML manual is http://orgmode.org/org.html, which downloads the entire contents of the manual into the browser. This is perhaps tolerable on a full-size computer, but if I want to check something using the browser on my tablet, the huge/immense/massive page grinds my tablet to a halt. This index works beautifully, though: http://orgmode.org/manual/index.html I think it might be helpful if the main org page gave users the choice whether they want to download the whole manual as one page, or browse separate pages for the various sections and subsections. OK, I have added such a link. - Carsten hjh
Re: [O] Upgrading orgmode
Vikas Rawal vikasli...@agrarianresearch.org writes: I normally upgrade my orgmode using sudo make up2, in the orgmode directory. But today when I did it, I get the following error: *** 3 unexpected results: FAILED test-org-export/data-with-backend FAILED test-org-export/export-snippet FAILED test-org-export/table-cell-alignment make[1]: *** [test-dirty] Error 1 make[1]: Leaving directory `/home/vikas/lisp/org-mode' make: *** [up2] Error 2 *** Looks like a bug to me. Could somebody check? Confirmed: Org-mode version 8.0.7 (release_8.0.7-380-g2a28de @ /home/nick/elisp/org-mode/lisp/) I chased the first one a bit and it fails in org-export-filter-apply-functions, in the following code: (let ((backend-name (org-export-backend-name (plist-get info :back-end The (plist-get info :back-end) call returns nil and when I call (org-export-backend-name nil) by hand, it does complain the same way: org-export-backend-name accessing a non-org-export-backend -- Nick
Re: [O] faster agenda with properties support disabled (no org-refresh-properties)
On 12.8.2013, at 05:43, Daniel Clemente n142...@gmail.com wrote: M-x elp-instrument-package org M-x elp-reset-all run your workload M-x elp-results Incidentally I ran that and I saw: org-agenda1 15.709354028 15.709354028 org-agenda-list 1 15.495628529 15.495628529 org-agenda-prepare1 8.388162561 8.388162561 org-agenda-prepare-buffers1 8.349513929 8.349513929 org-agenda-get-day-entries477 5.7457141640 0.0120455223 org-agenda-get-scheduled 477 2.0763930930 0.0043530253 org-agenda-get-timestamps 477 2.046089454 0.0042894957 org-set-regexps-and-options-for-tags 164 1.8202055340 0.0110988142 org-refresh-properties318 1.3865960840 0.0043603650 org-refresh-category-properties 159 1.1616332550 0.0073058695 org-agenda-get-deadlines 477 0.5512838650 0.0011557313 org-agenda-get-blocks 477 0.5356222019 0.0011228976 org-get-todo-state3581 0.4114158859 0.0001148885 org-agenda-get-sexps 477 0.4037585499 0.0008464539 … I looked at org-refresh-properties. In org.el there is: (defun org-agenda-prepare-buffers (files) … (org-refresh-category-properties) (org-refresh-properties org-effort-property 'org-effort) (org-refresh-properties APPT_WARNTIME 'org-appt-warntime) … Since I am not using effort/category/appointment properties in my agenda, I would like to disable it. I commented it in the code and I get the same agenda but 2'4 seconds faster (even more than 1'4 from org-refresh-properties). The new instrumentation report is: org-agenda1 13.345656663 13.345656663 org-agenda-list 1 13.113396681 13.113396681 org-agenda-prepare1 7.086576653 7.086576653 org-agenda-prepare-buffers1 7.054057855 7.054057855 org-agenda-get-day-entries477 5.7340928759 0.0120211590 org-agenda-get-scheduled 477 3.3844209709 0.0070952221 org-set-regexps-and-options-for-tags 164 1.8059163709 0.0110116851 org-refresh-properties318 1.3982702620 0.0043970762 org-refresh-category-properties 159 1.1513761240 0.0072413592 org-agenda-get-timestamps 477 0.6975214329 0.0014623090 org-agenda-get-deadlines 477 0.557952655 0.0011697120 org-agenda-get-blocks 477 0.533165758 0.0011177479 org-agenda-skip 3977 0.4244523499 0.0001067267 … So I would like to ask: is there a clean way to disable calls to org-refresh-properties? No, that would require a patch and a config variable. - Carsten
Re: [O] New exporter and dates in tables
OK, thank you. - Carsten On 9.8.2013, at 13:02, Bernt Hansen be...@norang.ca wrote: Hi Carsten! All of my headings are followed by an inactive timestamp. I've started leaving a blank line before the content for the heading so the inactive timestamp is not exported when timestamps are disabled with the :nil option. This works fine for me. Regards, Bernt Carsten Dominik carsten.domi...@gmail.com writes: Hi guys, did you arrive at a conclusion of this thread, or is this still open? Thanks - Carsten On 16.4.2013, at 09:48, Bastien b...@gnu.org wrote: Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: We can widen the definition of `standalone': a standalone timestamp is a timestamp belonging to a paragraph that contains only timestamps objects. Great. If that's possible, then I think that's the best solution. The following patch should do that. It comes with tests, but it should be tested extensively, if only to know if this feature is as useful as it seems. I think I nailed down the root of the confusion. org-export-with-planning does the job that org-export-with-timestamps used to do. So first of all, org-export-with-timestamps should be an alias to org-export-with-planning so that users who customized org-export-with-timestamps don't have to change their customization: (define-obsolete-variable-alias 'org-export-with-timestamps 'org-export-with-planning 24.4) Today, org-export-with-timestamps does a completely different job, more fine-grained than the old org-export-with-timestamps. I suggest to rename it to org-export-with-individual-timestamps and to use the latest patch you sent, with a default value of t. I expect the next useful value is 'not-standalone. But if someone wants to get rid of time-stamps in tables or in lists, he now can. Note that another option is to allow all timestamps, put timestamps you don't want to export in a specific drawer (e.g. TIME), and ignore this drawer during export. Yes, but that requires educating users, which I don't really like. Thanks, -- Bastien
