Bastien wrote: > Samuel Wales <samolog...@gmail.com> writes: > >> However, the COMMENT keyword on a headline stops results from showing. >> This is not desired. It is also inconsistent with commented lines. >> >> I strongly prefer for all matches to show up, whether commented or >> not. However, in principle there could be an option to not match >> anything that is commented. If such an option is desired, however, I >> suggest the safer value of nil as a default. > > There is such an option: > > (setq org-agenda-skip-comment-trees nil) > > It defaults to `t' which I think is a good default.
Isn't here the problem that the OP makes a difference between "agenda generation" and "results for a search". I guess he agrees COMMENTed trees should not participate in agendas, but well in regexp searches. Best regards, Seb -- Sebastien Vauban
