| commit | 2fcbd1d806a2f9856c8c76e83aed1ea775d9db4d | |
| author | Carsten Dominik <carsten.dominik@gmail.com> | |
| Wed, 16 Dec 2009 09:44:41 +0000 (16 10:44 +0100) | ||
| committer | Carsten Dominik <carsten.dominik@gmail.com> | |
| Wed, 16 Dec 2009 09:44:41 +0000 (16 10:44 +0100) | ||
| tree | 259403e3b9d43d990b9c7ae7737975dcfb49d1f0 | treesnapshot (tar.gz zip) |
| parent | 498e71da49e31fd67d73155115e423a251d4c6a9 | commitdiff |
Empty matcher means prompt in agenda custom commands
When an agenda custom command has an empty string as MATCH element, so
far this would lead to a meaningless search using an empty matcher.
Now and empty (or white) string will be interpreted just like a nil
matcher, i.e. the user will be prompted for the match.
When an agenda custom command has an empty string as MATCH element, so
far this would lead to a meaningless search using an empty matcher.
Now and empty (or white) string will be interpreted just like a nil
matcher, i.e. the user will be prompted for the match.
| lisp/ChangeLog | diffblobblamehistory | |
| lisp/org-agenda.el | diffblobblamehistory |