On Wed, 26 Mar 2008 05:28:03 -0500 "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> However, I got the following when I chose find-next-todo: > <type 'exceptions.AttributeError'>: 'tuple' object has no attribute > 'has_key' Hmm, I've tidied the code so that that function uses cleo's attribute getting method instead of doing the work itself, the attribute getting method includes a type check that will prevent the problem you saw. I can't remember a time when the 'annotate' uA was a tuple, so I don't know why you got that behavior, but it won't happen again. > P.S. I might enable cleo in leoSettings.leo, but I personally don't > like the coloring of @thin nodes. Is there any way I can disable > that feature? Blithely ignoring the feature freeze :-} I added a @string setting 'cleo_color_file_nodes' which, if set to "" (not None) will disable file node coloring. Cleo's node headstring foreground / background color functions all date back to the ancient primordial cleo I haven't changed much. I think the leo api should make changing those colors easier, and perhaps the ui should include controls to let the user change them too. No harm in cleo doing it, but it seems like something you should be able to do without cleo. Although I guess changing colors was the original purpose of prehistoric cleo :-) Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
