emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Alexander Gerds <tag@biostat.ku.dk>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org agenda extensions
Date: Sat, 12 Jan 2013 08:43:40 +0100	[thread overview]
Message-ID: <86sj66c0cz.fsf@biostat.ku.dk> (raw)
In-Reply-To: <87mwweeuaz.fsf@bzg.ath.cx> (Bastien's message of "Sat, 12 Jan 2013 08:26:12 +0100")

Hi Bastien

thanks for looking into this! I understand your general point of
view. however, the proposed changes would only slow down agenda creating
if org-agenda-property-list is set, right?

also, it certainly requires some insights to write
org-agenda-overriding-agenda-format which could display non-special
properties. hence only a user who knows what she/he is doing would run
into this problem.

anyway, could you propose a different approach to get this extension? I
could write a new function org-scan-properties, but that would require
several changes in org-agenda ...

thanks again,
Thomas

ps: one limitation of org-agenda-columns seems to be that columns
cannot be activated in two different agenda buffers simulaneously.






Bastien <bzg@altern.org> writes:

> Hi Thomas,
>
> I've reviewed the proposed change.
>
> `org-scan-tags' already does many things beyond its name, because
> a "tag" here is really a "match", which can include properties --
> see `org-make-tags-matcher' for how the "tags match" is built from
> properties).  
>
> This is handy for tags view and `org-sparse-tree'.
>
> In agenda, we don't need to display the properties that are part of
> the tag match, as they are part of the agenda headline already.
>
> I don't think we should let the user add properties to the agenda
> lines this way, as (1) it would make the name `org-scan-tags' even
> more confusing and (2) it would probably slow down agenda creating
> a lot -- `org-scan-tags' is the bottleneck for speed here.
>
> Also, the whole purpose of `org-agenda-columns' is precisely to see
> properties in agenda, so I'd rather let the user interactively decide
> if he wants to take the extra mile (and time) or not.
>
> 'hope this sounds reasonable enough.
>
> And thanks anyway for this!
--
Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics
University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark
Office: CSS-15.2.07 (Gamle Kommunehospital)
tel: 35327914 (sec: 35327901) 

  reply	other threads:[~2013-01-12  7:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 10:47 org agenda extensions Thomas Alexander Gerds
2013-01-11 16:26 ` Bastien
2013-01-11 20:50   ` Thomas Alexander Gerds
2013-01-12  7:26     ` Bastien
2013-01-12  7:43       ` Thomas Alexander Gerds [this message]
2013-01-12  8:43         ` Bastien
2013-01-12  9:03           ` Thomas Alexander Gerds
2013-01-12  9:25             ` Bastien
2013-01-12  9:36               ` Thomas Alexander Gerds
2013-01-11 13:35 Thomas Alexander Gerds

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=86sj66c0cz.fsf@biostat.ku.dk \
    --to=tag@biostat.ku.dk \
    --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).