Configuration: 'search.case.sensitive' now defaults to 'yes' on Cygwin

- A Cygwin bug appears to have been fixed.
This commit is contained in:
Paul Beckingham 2015-08-14 11:09:01 -04:00
parent cdc5b82e3f
commit d8e0cf714b
2 changed files with 2 additions and 4 deletions

2
NEWS
View file

@ -19,6 +19,8 @@ New configuration options in Taskwarrior 2.4.5
Both variations are imported.
- The 'color.uda.<name>.none' is a color that is applieѕ to tasks that do
not have a value for the UDA '<name>'.
- A Cygwin fix means that now we can default 'search.case.sensitive' to 'yes',
and all platforms are again equal.
Newly deprecated features in Taskwarrior 2.4.5

View file

@ -90,11 +90,7 @@ std::string Config::_defaults =
"column.padding=1 # Spaces between each column in a report\n"
"bulk=3 # 3 or more tasks considered a bulk change and is confirmed\n"
"nag=You have more urgent tasks. # Nag message to keep you honest\n" // TODO
#ifdef CYGWIN
"search.case.sensitive=no # Case-insensitive regex searches are broken under Cygwin\n"
#else
"search.case.sensitive=yes # Setting to no allows case insensitive searches\n"
#endif
"active.indicator=* # What to show as an active task indicator\n"
"tag.indicator=+ # What to show as a tag indicator\n"
"dependency.indicator=D # What to show as a dependency indicator\n"