Jack Kamm writes:
> Ihor Radchenko writes:
>
>> I agree that it makes sense.
>> However, it is technically a breaking change.
>> May you please add a news entry as well?
>
> Thanks, I've updated the patch with a news entry now.
Thanks!
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs
mestamps as a type of active timestamp for
+purposes of export.
+
+This mainly affects iCalendar export, where diary timestamps will now
+be included when only active timestamps are exported (the default).
+
+This should have minimal impact on non-iCalendar exporters, since
+~org-export-with-timestamps~ wa
Jack Kamm writes:
> ox-icalendar skips the following event with a diary timestamp during
> export:
>
> * First Sunday of the month
> <%%(diary-float t 0 1)>
>
> ox-icalendar actually has longstanding code to handle diary timestamps
> [1], but that code path is not reached, in part because
> `
cs)
(delete-file tmp-ics
+(ert-deftest test-ox-icalendar/diary-timestamp ()
+ "Test icalendar export of diary timestamps."
+ (let* ((tmp-ics (org-test-with-temp-text-in-file
+ "* First Sunday of the month
+<%%(diary-float t 0 1)>"
Ypo writes:
> I can't share my private org files. And I find myself unable to isolate
> the causes of the possible errors.
One strategy that might help is to "bisect" the Org file by repeatedly
splitting it into 2 files, and exporting each, to find where the
problematic entries are. By splittin
Thanks, Ihor
I can't share my private org files. And I find myself unable to isolate
the causes of the possible errors.
I think I will keep waiting till somebody shares an easy and robust way
to get an .ics calendar from org files.
Best!
On 02/02/2024 22:25, Ihor Radchenko wrote:
Ypo wri
files:
--8<---cut here---start->8---
DIARY=${HOME}/s/notes/diary
OUTLOOK=${HOME}/s/notes/outlook
emacs -Q --batch --debug-init \
--load=esf-org.el \
--visit=${DIARY}.org --eval='(org-icalendar-export-to-ics)' \
--visit=${OUTLOOK}.org
Ypo writes:
> I am sharing a bug report from emacs -q. I don't know how to use a
> different org-version that the built-in (or if I should).
Sorry for not being clear. Let me elaborate what I expect.
1. Create example Org file or a set of Org files, open them with
emacs -Q, and try to trigg
I am sharing a bug report from emacs -q. I don't know how to use a
different org-version that the built-in (or if I should).
Emacs : GNU Emacs 29.2 (build 2, x86_64-w64-mingw32)
of 2024-01-18
Package: Org mode version 9.6.15 (release_9.6.15 @
./emacs-i686/share/emacs/29.2/lisp/org/)
curren
Ypo writes:
> If I were able to fulfill a good process to export from agenda to
> icalendar, maybe we could share an easy process, useful for a lot of
> users that miss a good android calendar visualization. Do you think it
> could be possible to export, in an async way, a calendar file every
I got org updated, following Ihor's instructions: Org mode version
9.7-pre (release_N/A-N/A-afc529 @ ./org-9.7pre0.20240130.161905/)
If I were able to fulfill a good process to export from agenda to
icalendar, maybe we could share an easy process, useful for a lot of
users that miss a good and
ypuntot writes:
> Problem! Found 1 error
>
> Errors
> Lines not delimited by CRLF sequence near line # 1
> Reference: RFC 5545 3.1. Content Lines
Which version of Org are you using? (M-x org-version)
Org 9.7 (unreleased) contains some fixes for how ox-icalendar handles
newlines. If you are usin
The validator says as follows:
Results
File Size: 19544 lines, 434248 bytes
Number of events found: 103
Number of to-do's found: 541
Problem! Found 10 warnings
Warnings
Blank line detected, specification does not address the use of blank lines near
line # 9
Blank line detected, specification doe
Ihor Radchenko writes:
> CCing ox-icalendar maintainer.
>
> ypuntot writes:
>
>> I am trying to create an android calendar based on the agenda, and the first
>> problem I am finding it's that I can't import it into android (ICSx^5). I am
>> receiving these errors when trying to do it:
>>
>> Co
CCing ox-icalendar maintainer.
ypuntot writes:
> I am trying to create an android calendar based on the agenda, and the first
> problem I am finding it's that I can't import it into android (ICSx^5). I am
> receiving these errors when trying to do it:
>
> Couldn't parse iCalendar ...
May you
I am trying to create an android calendar based on the agenda, and the first
problem I am finding it's that I can't import it into android (ICSx^5). I am
receiving these errors when trying to do it:
Couldn't parse iCalendar at.bitfire.ical4android.InvalidCalendarException:
Couldn't parse iCale
Den sön 17 sep. 2023 kl 11:49 skrev Ihor Radchenko :
> Jack Kamm writes:
>
> >> Does the attached patch fix the problem for you?
> >
> > I can reproduce the bug by calling `org-icalendar-export-current-agenda'
> > in my agenda buffer. It seems to mainly hap
Jack Kamm writes:
>> Does the attached patch fix the problem for you?
>
> I can reproduce the bug by calling `org-icalendar-export-current-agenda'
> in my agenda buffer. It seems to mainly happen when subsequent agenda
> entries originate from different files.
>
> I
ply better to the icalendar
> specs and introduced new feature. As it usually goes, major changes can
> easily introduce new bugs.
>
> Does the attached patch fix the problem for you?
I can reproduce the bug by calling `org-icalendar-export-current-agenda'
in my agenda buffer. It seems
Henrik Frisk writes:
> Recently (not sure when) the ics output came out malformed and a newline is
> omitted between the end of one event and the beginning of another:
>
> END:VEVENT
> BEGIN:VEVENT
>
> is now
>
> END:VEVENTBEGIN:VEVENT
>
> I can't figure out wha the pattern is, for some events th
hi,
I've had an iCal export setup working fine for several years. I have an
org-agenda-custom-commands defined with:
(org-agenda-start-day "2022-09-01")
(org-agenda-span 120) ;; number of days
(org-agenda-include-diary nil))
Recently (not sure when) the ics output came out malformed and a newlin
Hanno Perrey writes:
> I have noticed a problem in =org-element-cache-map= that can be
> triggered under specific circumstances through
> =org-icalendar-export-to-ics= where the execution of the latter would
> simply hang apparently indefinitely. This happens if
>
> ...
>
Dear all,
I have noticed a problem in =org-element-cache-map= that can be
triggered under specific circumstances through
=org-icalendar-export-to-ics= where the execution of the latter would
simply hang apparently indefinitely. This happens if
- =org-icalendar-store-UID= set to ='t=
-
Dear Eliza,
On Tuesday, 15 Feb 2022 at 07:44, Eliza Velasquez wrote:
> It seems like `org-icalendar-export-to-ics' fails to consider the
> SCHEDULED and DEADLINE properties. Consider the following org file
> `foo.org':
By default, SCHEDULED and DEADLINE are properties of "
Hello,
It seems like `org-icalendar-export-to-ics' fails to consider the
SCHEDULED and DEADLINE properties. Consider the following org file
`foo.org':
* foo
SCHEDULED: <2022-02-15 Tue>
When invoking `org-icalendar-export-to-ics', we get the following
`foo.ics' file.
B
Hello,
msi writes:
> When I make the function "org-icalendar-combine-agenda-files", all it's
> ok. But, when I add a footnote, I have this in my .ics file :
>
> BEGIN:VEVENT.
> DTSTAMP:2026T101642Z.
> UID:SC-6a6cf716-f056-4116-a419-5f0e96b14fd9.
> DTSTART;VALUE=DATE:20220516.
> DTEND;VALUE=D
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hello!
I would like to have some more control over the alarms created by the
iCalendar export and was wondering if anyone has tried anything like
that, or has any surrounding thoughts?
Namely, I think it would be a nice feature if there could be some markup
(perhaps a property) that allows you
On Tuesday, 15 Dec 2020 at 16:37, Carson Chittom wrote:
> I've just started playing with the iCalendar export because eventually
> I want to keep everything in Org, to then get transformed and pushed
> to my CalDAV server, which then gets pushed to my phone.
You might like to try o
This is a very small thing, but it came up today for me, so I thought I'd
mention it. (Org 9.4.2, for the record.)
I've just started playing with the iCalendar export because eventually I want
to keep everything in Org, to then get transformed and pushed to my CalDAV
server, which
Fraga, Eric writes:
> Noting, of course, that you can have multiple time stamps (active ones
> in this case) associated with a single heading. I do this every so
> often.
Although it would be wonderful thing to have, but it does not affect
exported icalendar file. I was expecting that multiply t
On Wednesday, 12 Feb 2020 at 09:46, Bastien wrote:
> Perhaps adding three different appointments to get three alerts is
> good enough?
Noting, of course, that you can have multiple time stamps (active ones
in this case) associated with a single heading. I do this every so
often.
--
: Eric S Frag
Hi Mikhail,
Mikhail Skorzhinskii writes:
> I am happy with current functionality but in rare cases I'd like to have
> more reminders per entry. Like many other PIMs allows this
> today. E.g. I'd like to have at least 3 reminders for my flight
> appointments. So to be extra sure and do not to mis
Hi,
I am user of ox-icalendar package and I have a question about generating
reminders in icalendar files. Documentation says that proper way to
configure reminders is using org-icalendar-alarm-time variable and
setting APPT_WARNTIME property in cases when pre-entry customization
required.
I am h
Hello,
Eric Abrahamsen writes:
> Hey, now's the time to bring up something I've wanted to do for
> a while:
I think this deserves its own thread.
> adding support for per-entry timezones to the ical export.
It sounds good.
> I've attached a draft patch that shows what I mean. Basically you
Nicolas Goaziou writes:
> Hello,
>
> Tobias Schlemmer writes:
>
>> for some reasons I need to control the visibility of individual entries
>> of my caldav calendars. I have implemented a small patch that passes the
>> `CLASS' propery to the iCalendar export:
Hello,
Tobias Schlemmer writes:
> for some reasons I need to control the visibility of individual entries
> of my caldav calendars. I have implemented a small patch that passes the
> `CLASS' propery to the iCalendar export:
>
> https://github.com/keinstein/org-mode/pull/1
Hi,
for some reasons I need to control the visibility of individual entries
of my caldav calendars. I have implemented a small patch that passes the
`CLASS' propery to the iCalendar export:
https://github.com/keinstein/org-mode/pull/1
I'd like to have this patch integrated in the shor
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
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 n
Hi,
This is perhaps more of an Emacs issue than a problem with Org. When
trying to export my Org calendar in batch mode, I get the following:
$ emacs /home/loris/org/gtd.org -batch -eval '(progn (package-initialize)
(org-icalendar-export-to-ics))' --kill
Loading 00debian-vars...
Lo
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 perh
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. An
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 functi
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,
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
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 decl
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. <<>> <>
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 n
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
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 particul
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 p
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
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 l
Nicolas Goaziou writes:
> Interestingly, I introduced a patch that should speed up this function
> yesterday. You may want to update Org (the patch landed after 767895)
> and try again.
Indeed! I just pulled again and the problem is gone. The export runs
much more reasonably now, completing in
Org version is "8.3beta" (I am
> currently on commit 767895...)
>
> I have traced the problem down to a call to
> `org-icalendar-export-current-agenda', though I don't know if the
> problem is in this function or in another function called by it.
> Somewhere
; My Emacs version is 23.4.1 and my Org version is "8.3beta" (I am
> currently on commit 767895...)
>
> I have traced the problem down to a call to
> `org-icalendar-export-current-agenda', though I don't know if the
> problem is in this function or in another functio
rrently on commit 767895...)
I have traced the problem down to a call to
`org-icalendar-export-current-agenda', though I don't know if the
problem is in this function or in another function called by it.
Somewhere during the execution of this function, Emacs goes to 100% CPU
usage (on one co
Hi Daniel,
"Daniel E. Doherty" writes:
> Is there a way to supress running code block in the case of 'icalendar
> exports?
See `org-export-babel-evaluate'.
> I guess out of curiosity, is it a good idea to be executing them by
> default for this exporter?
Well, maybe for some people :)
--
B
I sync my org calendar with my Android phone by periodically running a
process that exports my agenda files in iCal format. I have this run
periodically, once every four hours or so.
My problem is that in combining the agenda files the exporter appears to
tangle the file, or in some way run the
Nicolas Goaziou writes:
> I went a bit further. Footnotes will always be ignored in ics
> export.
Great, thanks!
--
Bastien
Richard Lawrence writes:
> Here is a patch for a couple of tiny issues I encountered in ox-ascii.el
> while debugging ox-icalendar.el. Explanation:
I applied the changes. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Bastien writes:
>
>> I've been trying to get iCalendar export working with my agenda files
>> again since upgrading to 8.0, and I've found that footnotes break the
>> agenda export to .ics. The problem is that a plain text version of the
>> footno
Hello,
Richard Lawrence writes:
> I've been trying to get iCalendar export working with my agenda files
> again since upgrading to 8.0, and I've found that footnotes break the
> agenda export to .ics. The problem is that a plain text version of the
> footnotes in the file
Here is a patch for a couple of tiny issues I encountered in ox-ascii.el
while debugging ox-icalendar.el. Explanation:
1) There is no function called `org-ascii-footnote-definition' (though
it looks like maybe there once was?), so I changed a reference to it to
`ignore' to be more explicit.
I'm
Hi Bastien,
Bastien writes:
> Richard Lawrence writes:
>
>> I've been trying to get iCalendar export working with my agenda files
>> again since upgrading to 8.0, and I've found that footnotes break the
>> agenda export to .ics. The problem is that a plain t
Hi Richard,
Richard Lawrence writes:
> I've been trying to get iCalendar export working with my agenda files
> again since upgrading to 8.0, and I've found that footnotes break the
> agenda export to .ics. The problem is that a plain text version of the
> footnotes in t
Hi Org maintainers,
I've been trying to get iCalendar export working with my agenda files
again since upgrading to 8.0, and I've found that footnotes break the
agenda export to .ics. The problem is that a plain text version of the
footnotes in the file ends up in the output "
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
>
> Chan
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 e
cstring 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.
le'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.
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 se
* Bastien wrote:
> Hi Karl,
Hi!
> Karl Voit writes:
>
>> I'd love to have my agenda exported (for now I am using the snippet
>> below[1]) to an ics file which only contains (anonymized) events
>> optionally still containing (a set of allowed) tags.
>
> The new iCalendar exporter allows filters
Hi Karl,
Karl Voit writes:
> I'd love to have my agenda exported (for now I am using the snippet
> below[1]) to an ics file which only contains (anonymized) events
> optionally still containing (a set of allowed) tags.
The new iCalendar exporter allows filters -- so you should be able to
filter
Hi!
I'd love to have my agenda exported (for now I am using the snippet
below[1]) to an ics file which only contains (anonymized) events
optionally still containing (a set of allowed) tags.
So an event like:
** Meeting with ClientX <2013-01-17 Thu 17:00-18:30> :ProjectY:@town:
:PROPERTIE
This is now also fixed, thanks!
Friedrich Delgado schrieb:
> However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
> customisation, scheduled date-ranges are not exported at all (no
> matter what org-icalendar-use-scheduled is set to).
>
> ( 49905a566970541de76b6d49004c62e50c625a98 f
Hi Friedrich,
Friedrich Delgado writes:
> Friedrich Delgado schrieb:
>> confirmed, latest org does the right thing[TM]
>
> However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
> customisation, scheduled date-ranges are not exported at all (no
> matter what org-icalendar-use-schedu
Friedrich Delgado schrieb:
> confirmed, latest org does the right thing[TM]
However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
customisation, scheduled date-ranges are not exported at all (no
matter what org-icalendar-use-scheduled is set to).
( 49905a566970541de76b6d49004c62e50c
confirmed, latest org does the right thing[TM]
Bastien schrieb:
> Hi Friedrich,
>
> Friedrich Delgado writes:
>
> > 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
Hi Friedrich,
Friedrich Delgado writes:
> 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-f
Hi Friedrich,
Friedrich Delgado writes:
> 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-f
Hi!
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
,[
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
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-argume
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
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("\30
Thu 10:00-11:00>
> <2012-04-10 Tue 12:00-13:00>
> <2012-04-18 Wed 11:00-11:30>
> <2012-04-25 Wed 10:00-11:00>
> <2012-05-10 Thu 12:00-13:00>
>
> They should show up at any date/time listed there. That's true for the
> org agenda w
list.
I use the icalendar export to feed my schedule into the google calendar
(only one-way: Org -> Google). Basically that works fine (except for
google not understanding Umlauts...), but there's a big problem with
entries that contain more than one ti
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, th
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
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 c
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. Fr
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 e
Carsten Dominik writes:
> this code is not in Org mode.
now
^^^
-Bernt
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-o
Hi Eric,
this code is not in Org mode.
Thanks!
- Carsten
On Jul 11, 2010, at 12:26 AM, Eric S Fraga wrote:
Carsten et al.,
Okay, I've tried following the instructions for submitting patches.
I've learned more git than I thought I needed the past few days... ;-)
Anyway, I've uploaded my cha
On Jul 11, 2010, at 12:26 AM, Eric S Fraga wrote:
Carsten et al.,
Okay, I've tried following the instructions for submitting patches.
I've learned more git than I thought I needed the past few days... ;-)
Anyway, I've uploaded my changes to
git://github.com/ericsfraga/esf-org.git
under bran
Carsten et al.,
Okay, I've tried following the instructions for submitting patches.
I've learned more git than I thought I needed the past few days... ;-)
Anyway, I've uploaded my changes to
git://github.com/ericsfraga/esf-org.git
under branch "icalalarm" assuming I've done things correctly.
> > It seems org behaves correctly, and there's only an issue with
> > KOrganizer. So I'll knock on their doors. ;-)
>
> Great.
Haha, that sounds kinda maliciously. ;-)
> Another option would be of course a deadline with 0 warning days in
> there. This would show up as a due date.
Yes, but o
1 - 100 of 150 matches
Mail list logo
