[-- Attachment #1: Type: text/plain, Size: 885 bytes --] Does Org Mode have a way to identify that multiple events refer to the same event? It would be wonderful, for those of us with messy org files (multiple overlapping incoming data sources), if Org Mode had a way to to relate multiple events in a way that sums the details between events. For example, assuming I had two org files, customer.org and calendar.org (calendar.org being some form of exported ical-file): ~/customer.org: * TODO Meeting with Pete :PROPERTIES: :See: [[file:calendar.org:*Meet%20Pete][Meet Pete]] :END: ~/calendar.org: * Meet Pete SCHEDULED: <2013-04-19 Fri 09:30-10:00> When exported into an agenda, the consolidated org agenda would read: Friday 19 April 2013 customer: 09:00-09:30 Scheduled: TODO Meeting with Pete Are these wild dreams just dreams, or does Org Mode support such lovely magic? Nick [-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
Hi Nick,
Nick M. Daly <nick.m.daly@gmail.com> writes:
> When exported into an agenda, the consolidated org agenda would read:
>
> Friday 19 April 2013
> customer: 09:00-09:30 Scheduled: TODO Meeting with Pete
>
> Are these wild dreams just dreams, or does Org Mode support such lovely
> magic?
The problem is: what would RET do on this agenda line? Go to which
entry? You can always put some hacks in `org-agenda-finalize-hook'
but it's easier to try to keep your Org files clean ;)
--
Bastien
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --] Hi Bastien, thanks for the prompt reply. Bastien writes: >> When exported into an agenda, the consolidated org agenda would read: >> >> Friday 19 April 2013 >> customer: 09:00-09:30 Scheduled: TODO Meeting with Pete > > The problem is: what would RET do on this agenda line? Go to which > entry? You can always put some hacks in `org-agenda-finalize-hook' > but it's easier to try to keep your Org files clean ;) I would assume that RET would jump to the source item (the one with the "See also" property). It's unfortunately difficult for me to keep my source files clean: my schedule is composed of three different and unrelated sources, which vary daily. I export those sources to three different org files and combine those with my personal schedule to figure out what needs to be done every day. Since the exported sources get overwritten, I have to copy each event into my own (clean) org file and then unschedule the exported one, to keep the agenda clean. It's... silly, but it mostly works. If anybody wants a spreadsheet-to-org-file exporter, just let me know. :) Nick [-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
"Nick M. Daly" <nick.m.daly@gmail.com> writes:
> Hi Bastien, thanks for the prompt reply.
>
> Bastien writes:
>
>>> When exported into an agenda, the consolidated org agenda would read:
>>>
>>> Friday 19 April 2013
>>> customer: 09:00-09:30 Scheduled: TODO Meeting with Pete
>>
>> The problem is: what would RET do on this agenda line? Go to which
>> entry? You can always put some hacks in `org-agenda-finalize-hook'
>> but it's easier to try to keep your Org files clean ;)
>
> I would assume that RET would jump to the source item (the one with the
> "See also" property).
If I were using this, I would forget to mark any "See also", or else I
would do it, and forget I had already done so, and end up marking _both_
of them "See also". :)
Knowing that you have an entry elsewhere for this person or that event,
might give you the opportunity to do some kind of clever tricks with
links...
--
David R