Re: [O] iCalendar export and missed deadlines.
Hello, Michaël Cadilhac writes: > Is there a way to change this behavior so that the item is duplicated > as long as it's not DONE? I don't think so. > If not, where is a good starting point in ox-icalendar.el to hack this > in? `org-icalendar-entry' dispatches a headline (ENTRY), to various workers (e.g., `org-icalendar--vevent'). I would start from there. Regards, -- Nicolas Goaziou
[O] iCalendar export and missed deadlines.
Hi there; When I miss a deadline and scheduled todo, the org-agenda neatly prints the item until I've turned it to DONE. In iCalendar export, I expect/wish that it is also the case when deadlines and scheduled todos are exported as Events (I use VEVENT's as Google Calendar seems to not support VTODO's). By default, this is not the case, and the todo is simply put in the past by the iCalendar export. Is there a way to change this behavior so that the item is duplicated as long as it's not DONE? If not, where is a good starting point in ox-icalendar.el to hack this in? Thanks very much; Cheers
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > Well, I had intended the link target to become visible but now that > you ask, my primary concern was "not wrecking the export". I expect > that tel links are only relevant to the vcard export, which handles > them on its own terms (and which still works). > > So perhaps the patch is a bit premature. Any export function would > need not to interfere with the vcard handling, which is why > I refrained from adding one. Since no one chimed in, I applied your patch. We'll see if something is left to be done (e.g., defining a better export function). Thank you. Regards, -- Nicolas Goaziou
Re: [O] Icalendar export and contacts
Well, I had intended the link target to become visible but now that you ask, my primary concern was "not wrecking the export". I expect that tel links are only relevant to the vcard export, which handles them on its own terms (and which still works). So perhaps the patch is a bit premature. Any export function would need not to interfere with the vcard handling, which is why I refrained from adding one. Cheers, Simon On 02/20/2016 01:55 PM, Nicolas Goaziou wrote: Hello, Simon Thum writes: would the attached patch be enough? Thank you. I do not maintain org-contact.el, tho. +;; Add the link type supported by org-contacts-strip-link +;; so everything is in order for its use in Org files +(org-add-link-type "tel") This means that no export function is defined for "tel" links. Is it the intended behaviour? Regards,
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > would the attached patch be enough? Thank you. I do not maintain org-contact.el, tho. > +;; Add the link type supported by org-contacts-strip-link > +;; so everything is in order for its use in Org files > +(org-add-link-type "tel") This means that no export function is defined for "tel" links. Is it the intended behaviour? Regards, -- Nicolas Goaziou
Re: [O] Icalendar export and contacts
Then let's just hope it got fixed by accident ;) On 02/14/2016 05:49 PM, Nicolas Goaziou wrote: Hello, Simon Thum writes: Yes, but the exporter stalls on the [[fails]] link although it resolves in org. Provided you're right the reasoning seems off. I cannot reproduce it. Regards,
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > Yes, but the exporter stalls on the [[fails]] link although it > resolves in org. Provided you're right the reasoning seems off. I cannot reproduce it. Regards, -- Nicolas Goaziou
Re: [O] Icalendar export and contacts
Hi, would the attached patch be enough? Cheers, Simon On 02/12/2016 11:41 PM, Nicolas Goaziou wrote: Hello, Simon Thum writes: do you refer to master, maint or something else? I'm on 8.3 but am considering an upgrade. Development version = master. Also I think org-contacts should declare the link type if it has support for it (in the vcard export). I'd be happy to do that if it can be done as a TINYCHANGE. org-contacts is in contrib/ directory. TINYCHANGE tag is not required. Regards, >From fe28fb1eec7b8435f2ce9d30853fc3df707149c4 Mon Sep 17 00:00:00 2001 From: Simon Thum Date: Sat, 13 Feb 2016 17:20:05 +0100 Subject: [PATCH] Register tel link from org-contacts This has the added benefit of not screwing up the exporter. Signed-off-by: Simon Thum --- contrib/lisp/org-contacts.el | 5 + 1 file changed, 5 insertions(+) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 3236a7c..1aa2cab 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -1113,6 +1113,11 @@ link string and return the pure link target." (setq colonpos (string-match ":" link)) (if startpos (substring link (1+ colonpos)) link) +;; Add the link type supported by org-contacts-strip-link +;; so everything is in order for its use in Org files +(org-add-link-type "tel") + + (defun org-contacts-split-property (string &optional separators omit-nulls) "Custom version of `split-string'. Split a property STRING into sub-strings bounded by matches -- 2.1.3
Re: [O] Icalendar export and contacts
On 02/12/2016 11:43 PM, Nicolas Goaziou wrote: Hello, Simon Thum writes: I noticed one more strange thing: the new exporter fails to resolve links to radio targets (which are slightly pointless but worked before). I'm not sure it needs fixing, just thought I'd let you know. I.e. <<>> <> [[works]] [[fails]] It doesn't need to be fixed. Radio targets bring their own linking mechanism. Yes, but the exporter stalls on the [[fails]] link although it resolves in org. Provided you're right the reasoning seems off. Cheers, Simon
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > I noticed one more strange thing: > > the new exporter fails to resolve links to radio targets (which are > slightly pointless but worked before). I'm not sure it needs fixing, > just thought I'd let you know. > > I.e. <<>> <> > > [[works]] > [[fails]] It doesn't need to be fixed. Radio targets bring their own linking mechanism. Regards, -- Nicolas Goaziou
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > do you refer to master, maint or something else? I'm on 8.3 but am > considering an upgrade. Development version = master. > Also I think org-contacts should declare the link type if it has > support for it (in the vcard export). I'd be happy to do that if it > can be done as a TINYCHANGE. org-contacts is in contrib/ directory. TINYCHANGE tag is not required. Regards, -- Nicolas Goaziou
Re: [O] Icalendar export and contacts
I noticed one more strange thing: the new exporter fails to resolve links to radio targets (which are slightly pointless but worked before). I'm not sure it needs fixing, just thought I'd let you know. I.e. <<>> <> [[works]] [[fails]] Cheers, Simon On 02/12/2016 12:01 AM, Nicolas Goaziou wrote: Hello, Simon Thum writes: Unfortunately I now get user-error: Unable to resolve link "tel:xxx" and the icalendar export full stops. Is there a way to declare the link type (I am loading org-contact) See `org-add-link-type' in particular with the export argument. or avoid the exporter messing with it? This is only possible in development version. Regards,
Re: [O] Icalendar export and contacts
Hi, do you refer to master, maint or something else? I'm on 8.3 but am considering an upgrade. Also I think org-contacts should declare the link type if it has support for it (in the vcard export). I'd be happy to do that if it can be done as a TINYCHANGE. Cheers, Simon On 02/12/2016 12:01 AM, Nicolas Goaziou wrote: Hello, Simon Thum writes: Unfortunately I now get user-error: Unable to resolve link "tel:xxx" and the icalendar export full stops. Is there a way to declare the link type (I am loading org-contact) See `org-add-link-type' in particular with the export argument. or avoid the exporter messing with it? This is only possible in development version. Regards,
Re: [O] Icalendar export and contacts
Hello, Simon Thum writes: > Unfortunately I now get > > user-error: Unable to resolve link "tel:xxx" > > and the icalendar export full stops. Is there a way to declare the > link type (I am loading org-contact) See `org-add-link-type' in particular with the export argument. > or avoid the exporter messing with it? This is only possible in development version. Regards, -- Nicolas Goaziou
[O] Icalendar export and contacts
Hi all, I'm using the icalendar exporter and the vcard export in org-contacts. I use the [[tel:xxx]] links as they help keep things clean. Unfortunately I now get user-error: Unable to resolve link "tel:xxx" and the icalendar export full stops. Is there a way to declare the link type (I am loading org-contact) or avoid the exporter messing with it? I did not find such a possibility in the manual. In my use case, synchronization,, I don't care too much about the links being "resolved", I care about my export not failing badly. Thanks in advance, Simon
Re: [O] iCalendar export problem
Hello, Simon Thum writes: > However, that's not what DTSTAMP is for. Actually, it should be set to > the date-time the export happens. At least, that's what they say: > > http://stackoverflow.com/questions/11594921/whats-the-difference-between-created-and-dtstamp-in-the-icalendar-format > > Changing that probably does not help my problem, but seems better than > the cooked-up values now ending up in DTSTAMP. I could not see any > other candidate problems, though the analysis is weak so far. Thank you for the report. I pushed a fix for the DTSTAMP value. Is it better now? Regards, -- Nicolas Goaziou
[O] iCalendar export problem
Hi all, I have a strange problem that seems related to the iCalendar exporter. I have an event which has the date spec <2013-02-07 Th 12:00-14:00 +1w> but shows up on 13:00 my phone calendar (fed by ox-icalendar), CEST. Fun thing is, I did not experience lag with other entries. The org entry becomes: BEGIN:VEVENT DTSTAMP:20130207T11Z UID:TS1-d36d5eb9-e2db-42a3-866f-7442becadef0 DTSTART:20130207T12 DTEND:20130207T14 RRULE:FREQ=WEEKLY;INTERVAL=1 SUMMARY:Brown Bag Meeting DESCRIPTION:Location: R 103\n\nRecurs: <2013-02-07 Do 12:00 +1w>–<2013-02-07 Do 14:00 +1w> ... Another one (shown right this time) is: BEGIN:VEVENT DTSTAMP:20130404T15Z UID:TS1-441e317c-7b52-4910-bbd3-0949a5c1bdd7 DTSTART:20130404T17 DTEND:20130404T19 The difference seems to be the DTSTAMP which is "correctly" aligned with DTSTART. However, that's not what DTSTAMP is for. Actually, it should be set to the date-time the export happens. At least, that's what they say: http://stackoverflow.com/questions/11594921/whats-the-difference-between-created-and-dtstamp-in-the-icalendar-format Changing that probably does not help my problem, but seems better than the cooked-up values now ending up in DTSTAMP. I could not see any other candidate problems, though the analysis is weak so far. Cheers, Simon
Re: [O] Icalendar-export, priorities missing, possible bug
Hi, 2013-02-10 20:31, Nicolas Goaziou skrev: Hello, Anders Johansson writes: When I'm exporting to icalendar, the priorities of todo items (or perhaps any items) don't get carried through correctly. It always falls back to priority 5 (the default). After doing some edebugging I found that (string-match org-priority-regexp hd) [org-icalendar.el:539] never seems to match. This might be because 'hd' is group 4 "True headline" from the matching done with 'org-complex-heading-regexp' whereas group 3 according to this variable's docstring should hold the "Priority cookie". I guess someone who has greater knowledge of the code could see if this is really the case and fix it. I can provide more debugging output and examples if needed and if others can't reproduce this. iCalendar export back-end has been rewritten. It is accessible from the git distribution of Org. I didn't check if that bug is still present though. Regards, Oh, that looks completely different. Taking a look at the newest git source, priority is now found like this (ox-icalendar.el) 705 (let ((pri (or (org-element-property :priority entry) 706 org-default-priority))) and assuming this is consistent with the new framework it should of course work, but I haven't tested yet. Funny that I found this problem now, using the less than a week old ELPA-package (20130204), when the new export framework was "moved into core" (commit 8dd2bf) just three days ago. Greetings, Anders Johansson
Re: [O] Icalendar-export, priorities missing, possible bug
Hello, Anders Johansson writes: > When I'm exporting to icalendar, the priorities of todo items (or > perhaps any items) don't get carried through correctly. It always > falls back to priority 5 (the default). > > After doing some edebugging I found that > > (string-match org-priority-regexp hd) [org-icalendar.el:539] > > never seems to match. > > This might be because 'hd' is group 4 "True headline" from the > matching done with 'org-complex-heading-regexp' whereas group > 3 according to this variable's docstring should hold the "Priority > cookie". > > I guess someone who has greater knowledge of the code could see if > this is really the case and fix it. > > I can provide more debugging output and examples if needed and if > others can't reproduce this. iCalendar export back-end has been rewritten. It is accessible from the git distribution of Org. I didn't check if that bug is still present though. Regards, -- Nicolas Goaziou
[O] Icalendar-export, priorities missing, possible bug
Hi, When I'm exporting to icalendar, the priorities of todo items (or perhaps any items) don't get carried through correctly. It always falls back to priority 5 (the default). After doing some edebugging I found that (string-match org-priority-regexp hd) [org-icalendar.el:539] never seems to match. This might be because 'hd' is group 4 "True headline" from the matching done with 'org-complex-heading-regexp' whereas group 3 according to this variable's docstring should hold the "Priority cookie". I guess someone who has greater knowledge of the code could see if this is really the case and fix it. I can provide more debugging output and examples if needed and if others can't reproduce this. Greetings, Anders Johansson
Re: [O] Icalendar Export Broken in Git Version
Nick Dokos writes: Hi Nick: Thanks, Bastien already fixed it. > There are only two recent commits against org-icalendar. The second > one mentions org-print-icalendar-entries, so I bet that's the culprit > :-) I figured that it was that commit too when I grepped the git log. :-) > For future reference, if you can reproduce the problem with > *uncompiled* org-mode, the backtrace is going to be much more readable > (no byte code hieroglyphics). Just something to keep in mind. Thanks, I didn't know that. Charles -- "If you want to travel around the world and be invited to speak at a lot of different places, just write a Unix operating system." (By Linus Torvalds) pgpWkIFdtMEqf.pgp Description: PGP signature
Re: [O] Icalendar Export Broken in Git Version
Charles Philip Chan wrote: > Hello: > > I tried to export an icalendar file with the current git version of > org-mode and it failed. I debugged it by loading org-install on a clean > Emacs with no init files and this is what I got: > > , > | Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil) > | ... > | org-print-icalendar-entries(nil) > | ... > | org-export-icalendar(nil "/home/hoor/Desktop/Projects/plans/test.org") > | org-export-icalendar-this-file() > | call-interactively(org-export-icalendar-this-file record nil) > | command-execute(org-export-icalendar-this-file record) > | execute-extended-command(nil "org-export-icalendar-this-file") > | call-interactively(execute-extended-command nil nil) > ` > > If I replace org-icalendar with the version that comes with my Emacs > 24.1.50.1 everything works. > There are only two recent commits against org-icalendar. The second one mentions org-print-icalendar-entries, so I bet that's the culprit :-) , | commit 2cd498e16ddb8d321c2ab6e4fac18733b500 | Author: Bastien Guerry | Date: Sun Aug 5 18:59:51 2012 +0200 | | Fix two compiler warnings. | | commit 216768531f2661c4b1890eef6454f58e6cb8a241 | Author: Bastien Guerry | Date: Sun Aug 5 11:30:23 2012 +0200 | | org-icalendar.el: Let APPT_WARNTIME take precedence over ̀org-icalendar-alarm-time'. | | * org-icalendar.el (org-print-icalendar-entries): Let | APPT_WARNTIME take precedence over ̀org-icalendar-alarm-time'. ` For future reference, if you can reproduce the problem with *uncompiled* org-mode, the backtrace is going to be much more readable (no byte code hieroglyphics). Just something to keep in mind. Nick
Re: [O] Icalendar Export Broken in Git Version
Hi Charles, Charles Philip Chan writes: > I tried to export an icalendar file with the current git version of > org-mode and it failed. I debugged it by loading org-install on a clean > Emacs with no init files and this is what I got: Fixed, thanks for reporting this. -- Bastien
[O] Icalendar Export Broken in Git Version
Hello:
I tried to export an icalendar file with the current git version of
org-mode and it failed. I debugged it by loading org-install on a clean
Emacs with no init files and this is what I got:
,
| Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
| byte-code("\306 \210\203 \307 \310\216 *\204 \311
\210\312u\210\313\314\315\"\210\316\224\317\316!\320
\321\315\322\323\217@\324\325\315\326\"!A\324\325\315\327\"\206FB\205F\330
\321B#C\324\325\315\331\332#!DE\203_\333 \202f\334 \206f\335 F\336
G\325\315\337\"\211H\205z\340H!H\341I\315\211JK\342L!\203\237\316\225b\210\317\343!M\344\345M\"?\202\322e\nNZ]\n{O\344\346 \"\203\273\315\347\350\321\315 $\202\274 M\344PO\"J\344QO\"K\351
RS\204\346J\204\346K\204\346\313\314\321\"\210T\203\372\352\315\353\354\f\"\"\203\372\313\314\321\"\210J\203R\203\f\355U>?\202\356U>?\203\313\314\321\"\210K\2038R\203+\355V>?\2020\356V>?\2038\313\314\321\"\210J\203A\357\202KK\203J\360\202K\361W\344X@\"\204_\344Y@\"\203h\347\341\321\211@$@\344\362 \"\203\203\363\364\317\365 \"\366\"A\367\317\343 \"RZ\202\206\341ZA\206\215@A\315\370\371\217[H\316V\204\243\\\316V\203\310[@\203\310[A@\203\310\365[8\203\310\372\373AH\206\302\\#I\202\313\341I)\344]A\"\203\357\347\374\225\203\343\317\374A\"\202\350\317\343A\"\321\211A$AJ\203\372\375APAK\203\376APA\344\377 \"\203
[O] icalendar export skips todos with a scheduled time-range
Hello,
>From Debian bug #668496[0]:
If I have an org-file containing a todo with a scheduled date range, like
this:
,[ foo.org ]
*** TODO Weekend with the lads
SCHEDULED: <2012-05-04 Fr>--<2012-05-08 Di>
`
and try to export it via org-export-icalendar-this-file, the resulting
foo.ics will look like this
,[ foo.ics ]
BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:foo
PRODID:-//Friedrich Delgado//Emacs with Org-mode//EN
X-WR-TIMEZONE:Europe/Berlin
X-WR-CALDESC:nil
CALSCALE:GREGORIAN
END:VCALENDAR
`
(i.e.: contain no appointments at all)
I think the responsible section of code may reside in
/usr/share/emacs23/site-lisp/org-mode/org-icalendar.el, line 360:
,
(if (looking-at re2)
(progn
(goto-char (match-end 0))
(setq ts2 (match-string 1)
inc (not (string-match "[0-9]\\{1,2\\}:[0-9][0-9]" ts2
(setq tmp (buffer-substring (max (point-min)
(- pos org-ds-keyword-length))
pos)
ts2 (if (string-match
"[0-9]\\{1,2\\}:[0-9][0-9]-\\([0-9]\\{1,2\\}:[0-9][0-9]\\)" ts)
(progn
(setq inc nil)
(replace-match "\\1" t nil ts))
ts)
deadlinep (string-match org-deadline-regexp tmp)
scheduledp (string-match org-scheduled-regexp tmp)
todo (org-get-todo-state)
;; donep (org-entry-is-done-p)
))
`
From my basic understanding of the code-flow it looks like re2 ==
(concat "--?-?\\(" org-ts-regexp "\\)") is meant to match date-ranges,
but the code in the t branch of the if doesn't set deadlinep,
schedulep and todo, preventing all further processing of the entry.
But I may be wrong about the intentions of that function.
Cheers,
--Seb
[0] http://bugs.debian.org/668496
Re: [O] iCalendar export
Hi >>> And have anyone got this information to their mobile devices? Android? I do a simple two-way sync (well, kind of two-way) using the method described here: http://orgmode.org/worg/org-tutorials/org-google-sync.html ARUN
Re: [O] iCalendar export
Tassilo Horn writes: >> And have anyone got this information to their mobile devices? Android? > > Well, I have it there using the Google Calendar app. It's ok to see my > appointments in some graphical read-only view, but nothing more... I use some .ics files the same way Tassilo does. It's convenient to share with others. -- Bastien
Re: [O] iCalendar export
Gustav Wikström writes: Hi Gustav, > So my question to this newsgroup is; If you use the iCalendar export > function, what software do you use to view this information? Yeah, I convert to ical files on save, and there's some cron job that copies these files to some webpage. From there, I import into Google Calendar. But that doesn't show todos of imported ical files and has major encoding issues with german umlauts and so on. > And have anyone got this information to their mobile devices? Android? Well, I have it there using the Google Calendar app. It's ok to see my appointments in some graphical read-only view, but nothing more... Bye, Tassilo
[O] iCalendar export
Hello! I like the feature that TODO-items and calendar-items can be exportet to an iCalendar file. But one thing bugs me, I'm having trouble finding suitable software that supports the iCalendar-standard with vtodo items... So my question to this newsgroup is; If you use the iCalendar export function, what software do you use to view this information? And have anyone got this information to their mobile devices? Android? Having this information on the go would be killer... Regards Gustav
