From: Tassilo Horn <tsdh@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Tag inheritance broken in agenda/timeline buffers [7.9.3a (release_7.9.3a-803-gf8f548 @ /home/horn/Repos/el/org-mode/lisp/)]
Date: Thu, 10 Jan 2013 09:33:15 +0100 [thread overview]
Message-ID: <877gnl8mk4.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 87bocx8oud.fsf@thinkpad.tsdh.de
Tassilo Horn <thorn@fastmail.fm> writes:
> I have (all default values)
>
> org-use-tag-inheritance t
> org-agenda-use-tag-inheritance '(todo search timeline agenda)
> org-agenda-show-inherited-tags t
>
> but there are no inherited tags shown in the agenda or an org-buffer's
> timeline.
>
> When I press `T' on a agenda entry, the inherited tags are properly
> messaged in the echo area, though. I'm sure it used to work, but I'm
> not sure when it stopped working. When I find some time, I can try
> bisecting.
I've done the bisecting:
7684fbd6a227f0ad182661fd7eb17a9e13dc4695 is the first bad commit
commit 7684fbd6a227f0ad182661fd7eb17a9e13dc4695
Author: Nicolas Goaziou <n.goaziou@gmail.com>
Date: Tue Jan 8 10:34:40 2013 +0100
Ignore `auto-fill-inhibit-regexp'
* lisp/org.el (org-setup-filling): Ignore `auto-fill-inhibit-regexp'.
The idea behind this is that `org-adaptive-fill-function' already
determines which lines should be filled.
:040000 040000 a3246c36c59e412bd43df6afa0088d2499268265
7e69342d3b487a61a2cb6bba62b3262896fcdaab M lisp
Now don't ask me how that change affects tag inheritance?!
Bye,
Tassilo
next prev parent reply other threads:[~2013-01-10 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 7:43 Bug: Tag inheritance broken in agenda/timeline buffers [7.9.3a (release_7.9.3a-803-gf8f548 @ /home/horn/Repos/el/org-mode/lisp/)] Tassilo Horn
2013-01-10 8:33 ` Tassilo Horn [this message]
2013-01-10 8:36 ` Tassilo Horn
2013-01-10 8:55 ` Tassilo Horn
2013-01-10 10:45 ` Bastien
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=877gnl8mk4.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.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).