emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Nick M. Daly" <nick.m.daly@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Does Org support Related or "See Also" Properties?
Date: Sat, 20 Apr 2013 13:20:51 -0500	[thread overview]
Message-ID: <87wqrx9i7w.fsf@debian.home> (raw)
In-Reply-To: <87r4i5zn9e.fsf@bzg.ath.cx>

[-- 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. :)


[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-04-20 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20  1:49 Does Org support Related or "See Also" Properties? Nick M. Daly
2013-04-20  7:15 ` Bastien
2013-04-20 18:20   ` Nick M. Daly [this message]
2013-04-21  7:59     ` David Rogers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqrx9i7w.fsf@debian.home \
    --to=nick.m.daly@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).