emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Riley <rileyrgdev@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: floating, non scheduled agenda items
Date: Tue, 13 Apr 2010 16:03:19 +0200	[thread overview]
Message-ID: <86ae97-cdg.ln1@news.eternal-september.org> (raw)
In-Reply-To: 878w8rlbah.fsf@dasa3.iem.pw.edu.pl

Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:

> Richard Riley <rileyrgdev@gmail.com> writes:
>
>> Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
>>> Richard Riley <rileyrgdev@gmail.com> writes:
>>>> Richard Riley <rileyrgdev@gmail.com> writes:
>>>>
>>>>> What would be the best way to include in my daily agenda a section of
>>>>> non schedule items which are there every day until I decide to
>>>>> remove them.
>>> [...]
>>>> I needed to email Jan a little more for him to explain the procedure
>>> [...]
>>>> ,----
>>>> | You can replace the default agenda with a custom agenda if you specify
>>>> | "a" as the accesskey for the custom agenda.
>>> [...]
>>>> | - Jan
>>>> `----
>>>
>>> Personaly I'd recomend you leaving the default agenda intact and adding
>>> *your* own under 'A'. It's nice to have the *real* defaults at hand from
>>> time to time.
>>
>> I think this does use the real agenda doesn't it?
>
> It is indeed, however, you might want to customise the agenda further.

I don't want to modify the base agenda itself - only tag further info on
it. Hence the reuse of a. But yes, if I wanted something totally
different from the agenda it would be better to use a different key..

      reply	other threads:[~2010-04-13 14:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 20:02 floating, non scheduled agenda items Richard Riley
2010-04-09 21:37 ` Jan Böcker
2010-04-10 10:00 ` Richard Riley
2010-04-12 19:15   ` Łukasz Stelmach
2010-04-12 19:57     ` Richard Riley
2010-04-13 13:41       ` Łukasz Stelmach
2010-04-13 14:03         ` Richard Riley [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=86ae97-cdg.ln1@news.eternal-september.org \
    --to=rileyrgdev@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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