You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.
When using a formatted date string as a context, the Touch interface does not use the same pattern match as the CLI. Example:
@2011-01-11 is matched as a context in the CLI, Todo Touch only recognizes the same context as @2011
The text was updated successfully, but these errors were encountered:
Both context and project names only matched "word" characters. Basically
alphanumerics and underscore. There are often times where some internal
punction makes sense. (A project of todo.txt or a context of 2010-01-30)
This changes both expressions to match non-space characters, with the
final character being a word character. I added the last to not include
a potential final '.' or ',' if someone were adding the contexts or
projects by hand.
Both context and project names only matched "word" characters. Basically
alphanumerics and underscore. There are often times where some internal
punction makes sense. (A project of todo.txt or a context of 2010-01-30)
This changes both expressions to match non-space characters, with the
final character being a word character. I added the last to not include
a potential final '.' or ',' if someone were adding the contexts or
projects by hand.
Closestodotxt#74, closestodotxt#97
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using a formatted date string as a context, the Touch interface does not use the same pattern match as the CLI. Example:
@2011-01-11 is matched as a context in the CLI, Todo Touch only recognizes the same context as @2011
The text was updated successfully, but these errors were encountered: