search

robcowie / SublimeTODO

**[DEPRECATED]** - See https://github.com/jonathandelgado/SublimeTodoReview - Extract TODO-type comments from open files and project folders
295 stars 54 forks source link

Updated matching patterns #23

Closed emilbayes closed 9 years ago

emilbayes commented 12 years ago

After watching the video over at webdesign.tut+ I thought it would improve the UX of this project if the matching patterns ignored common comment endings. I have also added the very common XXX to signal a warning

emilbayes commented 12 years ago

Also updated Readme.md to reflect changes I made in todo.py. Please consider #1b7fe6a as this may cause fustration among users that FIXME and CHANGED can't have a space after the colon (unless this is intentionally)

robcowie commented 12 years ago

Nice idea, thanks.

I'm trying the patterns and they seem to miss loads of messages that should be matched. I'll try to find the time to pinpoint the problem; bit busy right now with work.

emilbayes commented 12 years ago

Can you give any examples? Then I'll try and solve it

robcowie commented 12 years ago

https://gist.github.com/2336769

Unless I'm being dim, the pattern changes cause non of the lines in that gist to be matched.

pztrick commented 12 years ago

I am using these patterns:

    'core_patterns': {

        'TODO': r'TODO[\s:]+(?P<todo>.*)$',

        'XXX': r'XXX[\s:]+(?P<xxx>.*)$',

        'NOTE': r'NOTE[\s:]+(?P<note>.*)$',

        'FIXME': r'FIX ?ME[\s:]+(?P<fixme>.*)$',

        'CHANGED': r'CHANGED[\s:]+(?P<changed>.*)$'

    },

And this is working well with matching either # TODO: lorem ipsum or # TODO dolor sic amet (without the colon) -- though I'm not sure what additional functionality I may have lost in my tweaks.

pkyeck commented 11 years ago

:+1: for the optional colon. thanks.

robcowie commented 9 years ago

All development of this plugin has ceased and moved to https://github.com/jonathandelgado/SublimeTodoReview