This shouldn't take any priority I imagine, but I am curious what causes it. If you execute M-x customize-group org-agenda RET at bottom you will find two appearances of subgroup `Org Agenda Match View', which I assume is not desired result. I think this must somehow result from Emacs' auto-documentation. Traveling through describe-function (for the contents "org-agenda-tags-todo-honor-ignore-options"), I arrive at agenda.el, and do some grepping. I found this, but I can't see anything wrong with it's lone appearance, ____ / (defgroup org-agenda-match-view nil "Options concerning the general tags/property/todo match agenda view." :tag "Org Agenda Match View" :group 'org-agenda) \____ Maybe I should have been doing some grepping elsewhere, but I'm lazy to go digging through Emacs source, which is probably in compiled form on this install (Linux. In my Windows install, default is for the source to be conveniently (inefficiently?) adjacent to the compiled.). Brady
Brady Trainor <algebrat@uw.edu> writes:
> This shouldn't take any priority I imagine, but I am curious what
> causes it.
>
> If you execute
>
> M-x customize-group org-agenda RET
>
> at bottom you will find two appearances of subgroup `Org Agenda Match
> View', which I assume is not desired result.
>
> I think this must somehow result from Emacs' auto-documentation.
>
> Traveling through describe-function (for the contents
> "org-agenda-tags-todo-honor-ignore-options"), I arrive at agenda.el,
> and do some grepping. I found this, but I can't see anything wrong
> with it's lone appearance,
> ____
> /
>
> (defgroup org-agenda-match-view nil
> "Options concerning the general tags/property/todo match agenda view."
> :tag "Org Agenda Match View"
> :group 'org-agenda)
>
> \____
>
> Maybe I should have been doing some grepping elsewhere, but I'm lazy
> to go digging through Emacs source, which is probably in compiled form
> on this install (Linux. In my Windows install, default is for the
> source to be conveniently (inefficiently?) adjacent to the compiled.).
>
If you look at the subsequent lines, you'll see that the next group was
probably cut-n-pasted from this one and has the wrong tag:
,----
| (defgroup org-agenda-match-view nil
| "Options concerning the general tags/property/todo match agenda view."
| :tag "Org Agenda Match View"
| :group 'org-agenda)
| (defgroup org-agenda-search-view nil
| "Options concerning the general tags/property/todo match agenda view."
| :tag "Org Agenda Match View"
| :group 'org-agenda)
`----
Nick
On 04/21/2014 01:28 PM, Nick Dokos wrote: > If you look at the subsequent lines, you'll see that the next group was > probably cut-n-pasted from this one and has the wrong tag: > | (defgroup org-agenda-search-view nil > | :tag "Org Agenda Match View" > Nick Thank you! It's reassuring that I sort of was getting it. With your find, I've been able to view the missing org-agenda-search-view-* vars that I didn't yet have in my grouped list of agenda-view/sparse-tree relevant variables. (They did exist somewhere in my notes, as I made a list of such options a while back by looking through every custom-commands example on the internet.) I think these variables should also be missing from the Variable Index (a list I'm just rediscovering) in the info pages for Org. Just guessing that they should be there. Brady
Hi Brady,
Brady Trainor <algebrat@uw.edu> writes:
> at bottom you will find two appearances of subgroup `Org Agenda Match
> View', which I assume is not desired result.
Indeed, fixed, thanks,
--
Bastien