Re: [O] [org-caldav] discerning calendars by color
Gour g...@atmarama.net 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 key, now everything is fine, it seems. Excuse me for the noise. :-( Sincerely, Gour -- You have a right to perform your prescribed duty, but you are not entitled to the fruits of action. Never consider yourself the cause of the results of your activities, and never be attached to not doing your duty.
Re: [O] Tiny typo in exported LaTeX code
Thank you!
2015-04-05 14:05 GMT-03:00 Nicolas Goaziou m...@nicolasgoaziou.fr:
Hello,
Vicente Vera vicente...@gmail.com 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] [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 properly, but I wonder how to manage to get different color for calendar entries on my phone? Every calendar is setup with different color on the ownCloud server, but they are rendered same in phone's calendar app. Previously I was trying to use different accounts (me my wife) and share each other's calendar, but then the problem is how to authorize users by having same 'machine' entry in my authinfo.gpg? Let me say that when using Evolution, I see different colors for each calendar both on the phone as well as in Evolution itself, but the whole point of using org-caldav (as well as org-vcard) is to be able to get rid of Evolution as well as GNOME stuff considering that I use Xfce. Another possibility could be to use some other WebDAV server (e.g. Baikal, Radicale) if, for whatever reason, there is problem between org-caldav OC, but considering that I have need to sync some multimedia stuff (mp3 recordings, phone's pics videos), I'd need another solution for syncing files (any recommendation?). Sincerely, Gour -- But for one who takes pleasure in the self, whose human life is one of self-realization, and who is satisfied in the self only, fully satiated — for him there is no duty.
Re: [O] Writing a letter with orgmode, hints ?
Carlos Sosa gnus...@gnusosa.net writes: Xavier Maillard xav...@maillard.im writes: Is there something to achieve that easily directly in an orgmode document ? I'm pretty sure I won't be the only one to tell you to export to LaTeX. You might want to look into Thanks a lot. I will try to use the koma-letter stuff as proposed by Vikas ! Cdt -- Xavier.
Re: [O] Writing a letter with orgmode, hints ?
Vikas Rawal vikasli...@agrarianresearch.org writes: I'd like to write letters and convert/export to something like PDF to be printed and sent. Is there something to achieve that easily directly in an orgmode document ? http://orgmode.org/worg/exporters/koma-letter-export.html Lovely ! -- Xavier.
[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-alist'). Note that if a keyword is parsed, its associated property (with prefix EXPORT_) will be, too. Macros are now expanded in any of them. As a side-effect, `org-element-context', which shouldn't depend on back-ends loaded, cannot return objects within TITLE, DATE and AUTHOR. This shouldn't affect `org-open-at-point', which now follows links within all keywords. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] Using macros in properties
Joon Ro joon...@outlook.com 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] 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 Emacs 24.5.1
Re: [O] [ANN] Parsed keywords no longer hard-coded
Hello, Rasmus ras...@gmx.us 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-latex. Anyway, feel free to introduce new behavior in back-ends. Regards, -- Nicolas Goaziou
Re: [O] Tiny typo in exported LaTeX code
Hello,
Vicente Vera vicente...@gmail.com 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
Re: [O] [ANN] Parsed keywords no longer hard-coded
Nicolas Goaziou m...@nicolasgoaziou.fr 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' behavior (see `org-export-options-alist'). Thanks a lot. 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. —Rasmus -- Send from my Emacs
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 org-code block 2) The +CALL line, at the end 3) The +CALL line, before the argument list (i.e., my_python_function[:cache yes](…)) None of these worked - the code was still re-evaluated when I exported the file, although the +RESULTS line got a hash value. Thank you very much, David David, Does this help? #+NAME: timenow #+BEGIN_SRC sh date #+END_SRC #+CALL: timenow[:eval never-export]() :eval never-export This will run interactively, but not on export. Instead the exported value of any previously saved `date' is exported. HTH, Chuck
