-
Notifications
You must be signed in to change notification settings - Fork 57
Closed
Description
Describe the bug
Taskwarrior 2.6.0 redefined the way context should be specified in the .taskrc. When using the new definition, vit will not start and throws the following error:
Traceback (most recent call last):
File "/usr/bin/vit", line 33, in <module>
sys.exit(load_entry_point('vit==2.1.0', 'console_scripts', 'vit')())
File "/usr/lib/python3.9/site-packages/vit/command_line.py", line 5, in main
Application(options, filters)
File "/usr/lib/python3.9/site-packages/vit/application.py", line 74, in __init__
self.refresh(False)
File "/usr/lib/python3.9/site-packages/vit/application.py", line 894, in refresh
self.bootstrap(load_early_config)
File "/usr/lib/python3.9/site-packages/vit/application.py", line 107, in bootstrap
self.load_contexts()
File "/usr/lib/python3.9/site-packages/vit/application.py", line 101, in load_contexts
self.contexts = self.task_config.get_contexts()
File "/usr/lib/python3.9/site-packages/vit/config_parser.py", line 327, in get_contexts
filters = shlex.split(re.sub(FILTER_PARENS_REGEX, r' \1 ', filters))
File "/usr/lib/python3.9/re.py", line 210, in sub
return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or bytes-like object
To Reproduce
Create a minimal .taskrc with the new context defninition
context.work.read=project:Work
context.work.write=project:Work
Expected behavior
Vit should open normally
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels