> See > https://list.orgmode.org/orgmode/CANvjMgnGkU3mCoJrkRVbHFw_z968hQgGb3bcA6aH5SG=pe9...@mail.gmail.com/ > That's the original implementation that solved the specific feature > request.
That confirms that the original motivation was the same as mine and performance was never a concern > Whether agenda could be changed - yes it can be. Not sure if it will be > easy, but certainly possible, if other people are also interested. But I checked, and it's not as easy as I expected. I thought that both limits and filters would apply on a list of entries removing some, and it was only a matter of changing the order of applying them, but it seems that's only true for limits, and filters are instead implemented making some agenda lines invisible. That makes the fix much more complex so if nobody has complained about this before I will just come up with a different workaround for my use case. >> Also, there is a specific case in which for me this is actually a bug >> or documentation should be improved: when there are blocked tasks and >> org-agenda-dim-blocked-tasks is set to 'invisible. In that case, >> limits are applied before ignoring blocked tasks, resulting in >> potentially less results than the number specified by the limit. Would >> it make sense to just ignore blocked tasks while constructing the >> agenda if org-agenda-dim-blocked-tasks is set to 'invisible? > I think that it is conceptually not different from filters. So, the > answer depends on whether the filters need to be applied before limiting. Ok, if you think this isn't a problem either, let's cancel the bug.
