emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Inherited tags not visible in agenda
Date: Wed, 9 Jan 2013 19:39:58 +0100	[thread overview]
Message-ID: <2013-01-09T19-29-19@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87zk0ii8mz.fsf@bzg.ath.cx

* Bastien <bzg@altern.org> wrote:
> Hi Karl,
>
> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> I just pulled the latest Org version but inherited tags still aren't
>> visible in my agenda.
>
> This is the current way of Org.

I see.

> Note that this is just about the "visible" tags.  If you hit 
> `T' on the agenda line, you should see inherited tags too if
> you have the default `org-agenda-use-tag-inheritance'.
>
> Which lets you have tag filtering okay... etc.

Indeed.

>> What is my problem that prevents inherited tags being visible in my
>> agenda?
>
> It is not a problem with *your* config... 

I was thinking of a config issue because up to my last git pull, all
inherited tags *were* visible in my agenda. Which I do like because
I tend to use inheritance for information.

For example, I am adding a meeting with one person to the contact
heading of that person (which is tagged with JohnSmith) and
therefore I see the link to John Smith when I use a simple
sub-heading for our meeting like: "*** <2013-01-09 10:00-11:00> Meeting" 

> I implemented this because it speeds up agenda generation *a
> lot* and those visible tags are just information.  

I do have a very poor performing agenda (approx. 121.000 lines of
Org) especially when I am querying my Memacs[1] data (additional
220.000 lines of Org in archive files).

However, since I use tag inheritance as a form of de-duplication, I
am willing to wait for them to be parsed :-)

> I'll clean up things and restore the previous behavior, but
> I want the current one to be available anyway.

A new standard behavior for speeding up agenda for lots of users is
fine to me as long as I am able to modify it to get previous
behavior sometime in the future. :-)

  1. https://github.com/novoid/Memacs
-- 
Karl Voit

  reply	other threads:[~2013-01-09 18:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 11:31 Org-mode release 7.9.3 Bastien
2013-01-08 13:11 ` Rainer Stengele
2013-01-08 13:30   ` Bastien
2013-01-08 14:00     ` Rainer Stengele
2013-01-08 14:36       ` Bastien
2013-01-09 15:03     ` Inherited tags not visible in agenda (was: Org-mode release 7.9.3) Karl Voit
2013-01-09 17:11       ` Inherited tags not visible in agenda Bastien
2013-01-09 18:39         ` Karl Voit [this message]
2013-01-11 16:36       ` Bastien
2013-01-11 17:50         ` habits don't get re-scheduled (was: Inherited tags not visible in agenda) Karl Voit
2013-01-12  6:33           ` habits don't get re-scheduled Bastien
2013-01-12 13:36             ` Karl Voit
2013-01-12 14:08               ` Bastien
2013-01-12 21:49                 ` Karl Voit
2013-01-13 15:31                   ` J. David Boyd
2013-01-13 19:02                     ` Karl Voit
2013-01-08 16:45 ` Org-mode release 7.9.3 J. David Boyd
2013-01-08 17:02   ` J. David Boyd
2013-01-08 17:40     ` Bastien
2013-01-09 14:56       ` J. David Boyd
2013-01-09 15:04         ` Nick Dokos
2013-01-10  0:59           ` J. David Boyd
2013-01-09 15:39         ` J. David Boyd

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=2013-01-09T19-29-19@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).