Re: [O] Tiny typo in exported LaTeX code

Thank you! 2015-04-05 14:05 GMT-03:00 Nicolas Goaziou : > Hello, > > Vicente Vera writes: > >> Hello. Just now I exported a minimal Org file to LaTeX (no fancy >> stuff, just a title, two headlines and harmless text) and the date is >> messed up. The offending line is: >> >> \date{$\backslash$oda

Re: [O] [org-caldav] discerning calendars by color

Gour writes: > Syncing with the server and my phone with DAVdroid seems to work properly, > but I wonder how to manage to get different color for calendar entries on my > phone? Ahh...soon after posting I got idea to change my org-caldav-calendars a bit and by using different entry for :inbox

[O] [org-caldav] discerning calendars by color

Hello, I've org-caldav-20150131.152 and using org-mode-8.2.10 (Emacs-24.4.1) and did setup using org-caldav-calendars in order to be able to sync two calendars which are in my case *two* calendars used by *one* ownCloud user. Syncing with the server and my phone with DAVdroid seems to work proper

Re: [O] [ANN] Parsed keywords no longer hard-coded

Hello, Rasmus writes: > I see you did not changed DESCRIPTION and KEYWORD in all backends. Unless > you plan to do it I'll look into this at the end of next week. I only changed them wherever they were actually parsed (using `org-element-parse-secondary-string'). This was only the case in "ox-

Re: [O] Only evaluate code blocks interactively, but export results

On Sat, 4 Apr 2015, David Dynerman wrote: Hi Tom, Does :cache yes work with #+CALL lines? I’m not able to get it to work. I’m calling my function through #+CALL’s because I’d like to generate several figures from the same org-babel code block/ I tried adding :cache yes to: 1) The actual or

Re: [O] [ANN] Parsed keywords no longer hard-coded

Nicolas Goaziou writes: > Parser used to have a hard-coded list of keywords that should be parsed, > namely "TITLE", "DATE" and "AUTHOR". This is no longer the case since > export back-ends can explicitly introduce new parsed keywords (e.g., > "SUBJECT" in "ox-koma-letter") with a `parse' behavio

Re: [O] Tiny typo in exported LaTeX code

Hello, Vicente Vera writes: > Hello. Just now I exported a minimal Org file to LaTeX (no fancy > stuff, just a title, two headlines and harmless text) and the date is > messed up. The offending line is: > > \date{$\backslash$oday} Fixed. Thank you. -- Nicolas Goaziou

[O] Tiny typo in exported LaTeX code

Hello. Just now I exported a minimal Org file to LaTeX (no fancy stuff, just a title, two headlines and harmless text) and the date is messed up. The offending line is: \date{$\backslash$oday} Org-mode version 8.3beta (release_8.3beta-1003-gfc790f @ /usr/local/share/emacs/site-lisp/org/) GNU Emac

Re: [O] Using macros in properties

Joon Ro writes: >> From: m...@nicolasgoaziou.fr >> >> This is not possible. >> > > Thanks for letting me know. :) Actually, this is now possible in development version. Truth is no match against Time. Regards,

[O] [ANN] Parsed keywords no longer hard-coded

Hello, Parser used to have a hard-coded list of keywords that should be parsed, namely "TITLE", "DATE" and "AUTHOR". This is no longer the case since export back-ends can explicitly introduce new parsed keywords (e.g., "SUBJECT" in "ox-koma-letter") with a `parse' behavior (see `org-export-options