On Sat, 8 Aug 2015 17:09:56 -0700 (PDT) john lunzer <lun...@gmail.com> wrote:
> I've actually been thinking about this for a long time, but I've > wanted to implement parts of the to-do plugin on purely text based > input. > > So a task that wasn't done would start with [ ] > A task that was finished would be [*] > and a task that was cancelled would be [x] > > Can I access the task icons in the same way that you're access the > icons currently with declutter? Sure, so the rules would be: RULE ^\[ ] (.*) REPLACE \1 ICON cleo/chkboxblk.png RULE ^\[\*] (.*) REPLACE \1 ICON cleo/chkblk.png RULE ^\[[xX]] (.*) REPLACE \1 ICON cleo/xblk.png `cleo` was the name of the plugin that preceeded `todo`, if you didn't know. Also I just updated the rules in leoSettings.py, they do the same thing, I just eliminated an editing artifact. They were like RULE ^@(clean) (.*) REPLACE \2 and are now like RULE ^@clean (.*) REPLACE \1 Cheers -Terry > On Saturday, August 8, 2015 at 1:52:20 PM UTC-4, Terry Brown wrote: > > > > On Sat, 8 Aug 2015 10:45:37 -0700 (PDT) > > john lunzer <lun...@gmail.com <javascript:>> wrote: > > > > > Not sure if you had come across this but different rules can > > > co-exist. For example along with all the @file type directives I > > > have .py files specifically bolded and both the rule for adding > > > the icon and the rule for bolding co-exist without issue. This > > > just keeps getting better! I assume there could be some issues if > > > the rules affected the same style aspects. > > > > The rules are just applied in sequence. Only gotcha is that if the > > first rule replaces `@clean ` with something else, subsequent rules > > that match `@clean ` won't fire - but I can't see when that would > > be a problem, and you can control the order. > > > > Cheers -Terry > > > > > On Saturday, August 8, 2015 at 1:39:03 PM UTC-4, john lunzer > > > wrote: > > > > > > > > Just pulled the most recent changes. Auto-update works great > > > > and the new icons look good. I'll be certain to let you know if > > > > I come across any issues. > > > > > > > > On Saturday, August 8, 2015 at 1:06:57 PM UTC-4, john lunzer > > > > wrote: > > > >> > > > >> Awesome, thanks for the quick updates, I'll check them out > > > >> soon (at the latest on Monday). > > > >> > > > >> On Saturday, August 8, 2015 at 12:44:44 PM UTC-4, Terry Brown > > > >> wrote: > > > >>> > > > >>> Also just pushed some icons for different @<file> types, with > > > >>> support for the leo_dark_0 theme. See updated rules in > > > >>> leo/config/leoSettings.leo#@settings-->Tree operation-->@data > > > >>> tree-declutter-patterns > > > >>> > > > >>> Cheers -Terry > > > >>> > > > >>> On Sat, 8 Aug 2015 08:59:35 -0500 > > > >>> "'Terry Brown' via leo-editor" <leo-e...@googlegroups.com> > > > >>> wrote: > > > >>> > > > >>> > On Fri, 7 Aug 2015 14:15:01 -0700 (PDT) > > > >>> > john lunzer <lun...@gmail.com> wrote: > > > >>> > > > > >>> > > One is that the conversions do not seem to take place > > > >>> > > until a certain action occurs in the tree. I can always > > > >>> > > get the conversions to happen from expanding a node (but > > > >>> > > not contracting a node). It also seems like sometimes the > > > >>> > > tree scrolls to a center a specific node after some > > > >>> > > conversions. > > > >>> > > > > >>> > I think these issues are fixed in the latest push. It was > > > >>> > tricky to get the update to work, it's done on idle so > > > >>> > you're outside any redraw loop. > > > >>> > > > > >>> > Cheers -Terry > > > >>> > > > > >>> > > > >> > > > > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
