Move color settings from taskrc to default.theme

[d2718nis]

Issue

As previously discussed, it would be beneficial to separate the default color theme from other configuration settings in taskrc. This change would ensure that new color settings don’t unintentionally bypass no-color.theme in case it omits them by mistake. Separating color settings would also improve the organization of configuration files.

Solution

Relocate all color. related settings from the default taskrc template to a new default.theme file. Use include default.theme to apply these color settings, like here.

[linsaraj]

Hi! This is my first time contributing and I would like to contribute/be assigned this good first issue if possible! Just so I understand, do you just want to move the .color settings into a newly created file named "default.theme" and then include that file using "#include" into the Context.cpp file? Does the .color settings include any lines that have .color in them (lines 210-280 in the Context.cpp file)?

[djmitche]

Hi @linsaraj! Yes, that's the idea! I think the #include would be added to

taskwarrior/src/Context.cpp

Lines 1182 to 1197 in fdb7e5e

	<< "\n# Color theme (uncomment one to use)\n"
	<< "#include light-16.theme\n"
	<< "#include light-256.theme\n"
	<< "#include bubblegum-256.theme\n"
	<< "#include dark-16.theme\n"
	<< "#include dark-256.theme\n"
	<< "#include dark-red-256.theme\n"
	<< "#include dark-green-256.theme\n"
	<< "#include dark-blue-256.theme\n"
	<< "#include dark-violets-256.theme\n"
	<< "#include dark-yellow-green.theme\n"
	<< "#include dark-gray-256.theme\n"
	<< "#include dark-gray-blue-256.theme\n"
	<< "#include solarized-dark-256.theme\n"
	<< "#include solarized-light-256.theme\n"
	<< "#include no-color.theme\n"