>> How to enforce useful keywords? > > To repeat from a later response: it's *easy* if "everything" of > interest is in a docstring. We enforce keywords with a script, like > the various checking scripts in leoSettings.leo and other places.
Speaking to "enforcement", I've never really grokked the utility of keywords. If everything is indexed for searching what are keywords needed for? On all the systems/environments which use keywords that I've spent time in there's a growing collection of things that don't quite fit. So the keywords are misused, and eventually lose their meaning, or just not used because people don't like looking them up. The utility of synonyms and alternate spellings on the other hand I get completely. ...hmm, remembering the context of this question, not having to dive into the details of every plugin source file in order to know who wrote it (:maintainer:) and when was it last known to work (:last_update:)... In this context keywords, or what I called trigger words moments ago, make perfect sense. I take it back. :-) I guess the difference is in scope and locality. When small in number and well defined in purpose keywords work very well. It's when we succumb to make them work in more circumstances and use more of them that utility decreases. It strikes me this might be similar, conceptually, to the difference between global and local variables. -matt -- 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.
