Terry>I think it would be more helpful if [the glossary] didn't start Terry> with all those @ entries - no doubt alphabetical order is Terry> working against us there.
+1 As an example, @settings is listed under "S" and not under Symbols -- this is a GOOD thing because as a newbie it's where I would look, not realizing that @settings was a special keyword. If I didn't see Settings under "S" I'd give up looking and think the docs were incomplete. Could we have the best of both worlds and have @ keywords under Symbols and under the entry based on the first character after the @? I like the idea of having all the @ keywords grouped together in one place. Since @ keywords seem to fall into two categories (I think?) -- body text directives and headline node directives(?) -- maybe in the Symbols section you could follow each keyword with a designation of where they can be used? That would create a quick reference arranged alphabetically. Not having much experience with Leo yet, sometimes just knowing where a keyword should be used is enough. Edward> This may be an issue with the standard .cssfile. I didn't do Edward> anything to set up the index: it just happened. Edward> Edward> Remember I've only begun to play with sphinx. Was it only three days Edward> ago that I figured out that conf.py controlled the index? The new glossary and index are looking really good! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
