emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "T. V. Raman" <raman@users.sf.net>
To: bzg@altern.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature Request: org-agenda-set-category
Date: Tue, 4 Sep 2007 19:16:17 -0700	[thread overview]
Message-ID: <18142.4465.2615.859169@gargle.gargle.HOWL> (raw)
In-Reply-To: <877in6e2fm.fsf@bzg.ath.cx>

Putting it immediately after the headline is how I would
implement it.

And it would work depending on ones workstyle --- most features
of org  make sense only in the context of a work style.

>>>>> "Bastien" == Bastien  <bzg@altern.org> writes:
    Bastien> "T. V. Raman" <raman@users.sf.net> writes:
    >> It would be nice to have an interactive
    >> org-agenda-set-category alongside org-agenda-set-tag in
    >> the agenda buffer.
    Bastien> 
    Bastien> I think it doesn't make sense to have
    Bastien> `org-agenda-set-category' until we are able to set
    Bastien> the category as a property of the headline.
    Bastien> 
    Bastien> For now categories (like the archiving locations)
    Bastien> are set by looking *backward* for a line like
    Bastien> #+CATEGORY or #+ARCHIVE.
    Bastien> 
    Bastien> When setting the category with
    Bastien> `org-agenda-set-category', where should such a line
    Bastien> be inserted/modified? Just above the headline? Then
    Bastien> storing this headline won't delete the #+CATEGORY
    Bastien> line. Just under the headline?  Then the headline
    Bastien> itself won't be recognized as belonging to that
    Bastien> category...  See the discussion here:
    Bastien> 
    Bastien>   http://article.gmane.org/gmane.emacs.orgmode/2898
    Bastien> 
    Bastien> Please anybody stops me if I'm wrong, but I guess
    Bastien> the #+ARCHIVE and #+CATEGORY instructions are slowly
    Bastien> dying and will be set as properties in the
    Bastien> future. We already (as of 5.07) have these new
    Bastien> properties when archiving:
    Bastien> 
    Bastien>   :ARCHIVE_TIME: 2007-09-01 sam 05:54 :ARCHIVE_FILE:
    Bastien> ~/org/bzg.org :ARCHIVE_CATEGORY: nothot
    Bastien> 
    Bastien> Then, in the new world, where such #+CONSTRUCTS are
    Bastien> only used to set *file* properties (not headlines
    Bastien> properties), it will be okay to set whatever
    Bastien> property you want through the column view -- and
    Bastien> perhaps the column view itself would be available in
    Bastien> the agenda ebuffer, which would let you have your
    Bastien> `org-agenda-set-category'.
    Bastien> 
    Bastien> (Of course #+CATEGORY will remain, but only as a way
    Bastien> to categorize files, not headlines.)
    Bastien> 
    >> This would allow one to quickly categorize tasks.
    Bastien> 
    Bastien> Yes, as the column view allows quick selection of
    Bastien> *any* property.
    Bastien> 
    >> Later, it might also be nice to implement a function that
    >> say rearranges all todo entries of a particular category
    >> under a common section. I find myself doing this by hand
    >> at present, and Emacs will probably do it better than my
    >> fingers.
    Bastien> 
    Bastien> Maybe `org-sort-entries' could group entries that
    Bastien> have a property in common.
    Bastien> 
    Bastien> -- Bastien
    Bastien> 
    Bastien> 
    Bastien> _______________________________________________
    Bastien> Emacs-orgmode mailing list Emacs-orgmode@gnu.org
    Bastien> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

-- 
Best Regards,
--raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

  reply	other threads:[~2007-09-05  2:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 13:18 Feature Request: org-agenda-set-category T. V. Raman
2007-09-04 18:00 ` Bastien
2007-09-05  2:16   ` T. V. Raman [this message]
2007-09-05  3:40   ` Carsten Dominik
2007-09-05  5:19     ` Bastien
2007-09-05  6:08       ` Carsten Dominik
2007-09-06  3:43     ` T. V. Raman
2007-09-06  5:34       ` Bastien
2007-09-06 13:25         ` T. V. Raman
2007-09-07  8:04         ` Carsten Dominik
2007-09-09 14:21           ` Nuutti Kotivuori
2007-09-13  5:44             ` Carsten Dominik
2007-09-10  1:00         ` Xavier Maillard
2007-09-06  9:25       ` Christian Egli
2007-09-05  1:00 ` Xavier Maillard

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=18142.4465.2615.859169@gargle.gargle.HOWL \
    --to=raman@users.sf.net \
    --cc=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).