Re: Feature Request: org-agenda-set-category

["T. V. Raman" <raman@users.sf.net>]

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