Re: [O] iCalendar export and missed deadlines.

[Nicolas Goaziou]

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

Re: [O] Icalendar export and contacts

[Nicolas Goaziou]

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

[Simon Thum]

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

[Nicolas Goaziou]

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

[Simon Thum]

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

[Nicolas Goaziou]

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

[Simon Thum]

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

[Simon Thum]

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  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

[Simon Thum]

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

[Nicolas Goaziou]

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

[Nicolas Goaziou]

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

[Simon Thum]

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

[Nicolas Goaziou]

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

Re: [O] iCalendar export problem

[Nicolas Goaziou]

Hello,

Simon Thum simon.t...@gmx.de 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

Re: [O] Icalendar-export, priorities missing, possible bug

[Nicolas Goaziou]

Hello,

Anders Johansson mejlaande...@gmail.com 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

Re: [O] Icalendar-export, priorities missing, possible bug

[Anders Johansson]

Hi,

2013-02-10 20:31, Nicolas Goaziou skrev:

Hello,

Anders Johansson mejlaande...@gmail.com 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 Broken in Git Version

[Bastien]

Hi Charles,

Charles Philip Chan cpc...@bell.net 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

Re: [O] Icalendar Export Broken in Git Version

[Nick Dokos]

Charles Philip Chan cpc...@bell.net 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 b...@altern.org
| Date:   Sun Aug 5 18:59:51 2012 +0200
| 
| Fix two compiler warnings.
| 
| commit 216768531f2661c4b1890eef6454f58e6cb8a241
| Author: Bastien Guerry b...@altern.org
| 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

[Charles Philip Chan]

Nick Dokos nicholas.do...@hp.com 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

[Arun Persaud]

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

[Bastien]

Tassilo Horn tass...@member.fsf.org 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

[Tassilo Horn]

Gustav Wikström gustav.e...@gmail.com 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