From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Categories
Date: Mon, 15 Oct 2007 18:54:33 +0100 [thread overview]
Message-ID: <87r6jwuuue.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jnr6jwtk1o.fsf@home.net> (Richard G. Riley's message of "Mon, 15 Oct 2007 18:33:07 +0200")
Richard G Riley <rileyrgdev@googlemail.com> writes:
>> (setq org-agenda-custom-commands
>> '(("r" tags-todo "Read/NEXT" nil)
>> ("w" tags-todo "Write/NEXT" nil)
>> ("R" tags-todo "Read/NEXT|TODO" nil)
>> ("W" tags-todo "Write/NEXT|INPROGRESS" nil)))
>
> Where do you press "r" or "R"? I have the code above and nothing happens
> in my agenda. Hopefully I am just being rather dim.
Check that the value of `org-agenda-custom-commands' is actually the one
above. Then run the command `org-agenda' --- you should see this at the
bottom left of the window:
r Tags (TODO) : Read/NEXT
w Tags (TODO) : Write/NEXT
R Tags (TODO) : Read/NEXT|TODO
W Tags (TODO) : Write/NEXT|INPROGRESS
> "C-c a m" then "Read" shows tasks with a tag of "Read". But pressing
> "r" or "R" does nothing.
If the "r" key (and its associated command) is not listed in the choice
you have when calling org-agenda, then it's normal that it does nothing.
Double-check for the value org `org-agenda-custom-commands' before doing
C-c a
NB: http://orgmode.org/org.html#Agenda-views might also help somehow
--
Bastien
next prev parent reply other threads:[~2007-10-15 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 23:05 Categories Richard G Riley
2007-10-12 3:16 ` Categories Eddward DeVilla
2007-10-12 9:00 ` Categories Richard G Riley
2007-10-12 13:31 ` Categories Bastien
[not found] ` <fgy7e85vf3.fsf@home.net>
2007-10-12 14:56 ` Categories Bastien
2007-10-12 14:12 ` Categories Richard G Riley
2007-10-12 14:27 ` Categories Carsten Dominik
2007-10-12 15:04 ` Categories Richard G Riley
2007-10-12 17:00 ` Categories Bastien
[not found] ` <qfr6k0b8f8.fsf@home.net>
[not found] ` <87bqb4uri3.fsf@bzg.ath.cx>
[not found] ` <ml641cb5wj.fsf@home.net>
[not found] ` <87r6k0tboe.fsf@bzg.ath.cx>
[not found] ` <0sprzk9pcu.fsf@home.net>
[not found] ` <87641cdniz.fsf@bzg.ath.cx>
[not found] ` <uzk5prdwxm.fsf@home.net>
[not found] ` <87tzovjeer.fsf@bzg.ath.cx>
[not found] ` <13k5prcg2a.fsf@home.net>
[not found] ` <87bqb3jcsm.fsf@bzg.ath.cx>
[not found] ` <77zlykith7.fsf@home.net>
2007-10-15 11:32 ` Categories Bastien
[not found] ` <jnr6jwtk1o.fsf@home.net>
2007-10-15 17:54 ` Bastien [this message]
[not found] ` <t1lka4thoz.fsf@home.net>
2007-10-15 18:38 ` Categories Bastien
[not found] ` <jbhcksjmnx.fsf@home.net>
2007-10-15 18:57 ` Categories Bastien
[not found] ` <2yd4vgdyxe.fsf@home.net>
2007-10-15 19:24 ` Categories Bastien
2007-10-12 17:07 ` Categories Carsten Dominik
2007-10-12 17:20 ` Categories Richard G Riley
2007-10-12 18:20 ` Categories Carsten Dominik
2007-10-13 12:22 ` Categories Richard G Riley
2007-10-14 6:14 ` Categories Carsten Dominik
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=87r6jwuuue.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).