From: Carsten Dominik <carsten.dominik@gmail.com>
To: Livin Stephen Sharma <livin.stephen@gmail.com>
Cc: emacs-org-mode-help gnu <emacs-orgmode@gnu.org>
Subject: Re: (new feature suggestion?) indicate 'repeater' nature in Agenda
Date: Tue, 6 Jul 2010 14:43:42 +0200 [thread overview]
Message-ID: <9153753C-F463-4F8D-9691-BC1B4ABB7B1A@gmail.com> (raw)
In-Reply-To: <8738FB76-3F91-4898-8251-13DB990540D0@gmail.com>
On Jul 2, 2010, at 8:57 AM, Livin Stephen Sharma wrote:
>
> Is there a way to quickly/visually differentiate between repeating/
> single-occurence tasks?
>
> If not, something like say, adding an asterisk somewhere in the
> entry would be great.
>
> 1. Scheduled* - starred schedule/deadline string
> 2. TODO * - starred 'todo' string
> 3. fifa2010* - starred 'category' string
>
> ( asking too much? J )
>
> I looked for org-agenda--repeat variables and searched 'repeat' in
> the pdf manual, but didn't find a way to do this..\
There is nothing in there right now, but it could be implemented.
Not sure how useful I would find this, though.
A simpler way would be (and this is what I do) this:
Collect stuff with repeating time stamps in one place and make sure the
category is special.
For example, I have
* Habits
:PROPERTIES:
:CATEGORY: habit
:END:
** Habit 1
** Habit 2
* Regular stuff
:PROPERTIES:
:CATEGORY: regular
:END:
** Item 1
** Item 2
>
> Thanks
> Livin Stephen Sharma
>
>
>
> _______________________________________________
> 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-orgmode
- Carsten
prev parent reply other threads:[~2010-07-06 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 6:57 (new feature suggestion?) indicate 'repeater' nature in Agenda Livin Stephen Sharma
2010-07-06 12:43 ` Carsten Dominik [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=9153753C-F463-4F8D-9691-BC1B4ABB7B1A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=livin.stephen@gmail.com \
/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).