On Tue, Feb 3, 2015 at 1:13 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
This starts happening when org-agenda-dim-blocked-tasks is set to
invisible. What seems to happen is that the blocked tasks, even though
they are invisible, are still counted towards org-agenda-max-entries.
Yuri Niyazov yuri.niya...@gmail.com writes:
Yes, that seems to me the behavior I am seeing. Are you saying that
this is not a bug?
It doesn't look like one.
It is certainly very surprising behavior. I had the make blocked
tasks invisible setting for months, and then only recently started
On Tue, Feb 3, 2015 at 2:12 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Documentation (e.g., docstrings) may be improved, then. Would you want
to suggest such an improvement?
In the docstring for org-agenda-dim-blocked-tasks
Because dimming is not the same as skipping, items dimmed to
Yuri Niyazov yuri.niya...@gmail.com writes:
I now think that having the ability to dim to invisible is a feature
mistake. I'm having a difficult time seeing when a user would want to
dim to invisible purely visually, rather than really skipping a
blocked task. There's no visual difference
Hello,
Yuri Niyazov yuri.niya...@gmail.com writes:
This starts happening when org-agenda-dim-blocked-tasks is set to
invisible. What seems to happen is that the blocked tasks, even though
they are invisible, are still counted towards org-agenda-max-entries.
AFAIU, even though they are
