search

davraamides / todotxt-mode

MIT License
59 stars 12 forks source link

Priority highlighting not working (Ubuntu) #1

Closed gohma231 closed 5 years ago

gohma231 commented 5 years ago

Priority highlighting does not work most of the time. I don't know what information to give to help you out with this though. I have attached a screenshot showing that the priorities do not highlight.

todotxt_colorBug

davraamides commented 5 years ago

HI,

Sorry, it's a mistake I accidentally committed and didn't notice right away. I will push the fix tonight and drop you a note.

-David

On May 22, 2019, at 3:43 PM, jgoulet1994 notifications@github.com wrote:

Priority highlighting does not work most of the time. I don't know what information to give to help you out with this though. I have attached a screenshot showing that the priorities do not highlight.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

gohma231 commented 5 years ago

No worries. This seems to be the only todotxt extension for VS Code that is actually working for Ubuntu users. Thank you for the extension!

davraamides commented 5 years ago

It's my first extension - and my first time using Typescript! So I'm just learning but I'm using it every day so will keep on top of this.

On Wed, May 22, 2019 at 3:46 PM jgoulet1994 notifications@github.com wrote:

No worries. This seems to be the only todotxt extension for VS Code that is actually working for Ubuntu users. Thank you for the extension!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/davraamides/todotxt-mode/issues/1?email_source=notifications&email_token=AAOOZGPUPY5QRAGBANTDGIDPWWPJ7A5CNFSM4HOXM25KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWADV5A#issuecomment-494942964, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOOZGL3SCW6A2MJMKXNNG3PWWPJ7ANCNFSM4HOXM25A .

davraamides commented 5 years ago

This issue is resolved with v1.4.2. A bad regex was the cause.