emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "T. V. Raman" <raman@users.sf.net>
To: dominik@science.uva.nl
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature Request: org-agenda-set-category
Date: Wed, 5 Sep 2007 20:43:22 -0700	[thread overview]
Message-ID: <18143.30554.285312.790877@gargle.gargle.HOWL> (raw)
In-Reply-To: <a21268bf7a20b9177adbc9d9853c8a39@science.uva.nl>

I'm perfectly happy to do this with properties rather than
categories. But I suggested categories because that is what
agenda  views are using at present in the left column.
Could we perhaps introduce a special property that is used by
org-agenda to build the left column?

>>>>> "Carsten" == Carsten Dominik <dominik@science.uva.nl> writes:
    Carsten> On Sep 4, 2007, at 20:00, Bastien wrote:
    Carsten> 
    >> "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.
    >> 
    >> I think it doesn't make sense to have
    >> `org-agenda-set-category' until we are able to set the
    >> category as a property of the headline.
    >> 
    >> For now categories (like the archiving locations) are set
    >> by looking *backward* for a line like #+CATEGORY or
    >> #+ARCHIVE.
    >> 
    >> When setting the category with `org-agenda-set-category',
    >> where should such a line be inserted/modified? Just above
    >> the headline? Then storing this headline won't delete the
    >> #+CATEGORY line. Just under the headline?  Then the
    >> headline itself won't be recognized as belonging to that
    >> category...  See the discussion here:
    >> 
    >> http://article.gmane.org/gmane.emacs.orgmode/2898
    >> 
    >> Please anybody stops me if I'm wrong, but I guess the
    >> #+ARCHIVE and #+CATEGORY instructions are slowly dying and
    >> will be set as properties in the future.
    Carsten> 
    Carsten> I have been thinking in this direction as well.  The
    Carsten> only problem is that properties are quite invisible
    Carsten> during normal working.
    Carsten> 
    Carsten> But I agree that the multiple #+CATEGORY things in a
    Carsten> single file are complex and not very clean, so
    Carsten> properties might be better.
    >> 
    >> Then, in the new world, where such #+CONSTRUCTS are only
    >> used to set *file* properties (not headlines properties),
    Carsten> 
    Carsten> Yes, I'd like to go there, eventually.
    Carsten> 
    >> it will be okay to set whatever property you want through
    >> the column view -- and perhaps the column view itself
    >> would be available in the agenda ebuffer
    Carsten> 
    Carsten> it is!
    Carsten> 
    Carsten> 
    Carsten> 
    Carsten> _______________________________________________
    Carsten> Emacs-orgmode mailing list Emacs-orgmode@gnu.org
    Carsten> 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

  parent reply	other threads:[~2007-09-06  3:43 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
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 [this message]
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=18143.30554.285312.790877@gargle.gargle.HOWL \
    --to=raman@users.sf.net \
    --cc=dominik@science.uva.nl \
    --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).