Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27212 - [task] creates wrong paths to default themes in ~/.taskrc
Attached to Project:
Community Packages
Opened by AbandonedAccount (montague) - Monday, 21 November 2011, 17:02 GMT
Last edited by Peter Lewis (petelewis) - Tuesday, 24 April 2012, 11:03 GMT
Opened by AbandonedAccount (montague) - Monday, 21 November 2011, 17:02 GMT
Last edited by Peter Lewis (petelewis) - Tuesday, 24 April 2012, 11:03 GMT
|
DetailsDescription: 'task' -- AKA taskwarrior -- automatically creates a user configuration file upon first time being run, but said file contains 'wrong' paths to the themes included. If you accept the default user config and then enable a theme, you will receive an error like this one:
Could not read include file '/usr/local/share/doc/task/rc/dark-green-256.theme'. Reason: There is no such path on Arch: /usr/local/share/doc/task/rc/ Paths in .taskrc should be changed to: /usr/share/doc/task/rc/... Additional info: * package version: task 1.9.4-2 * config and/or log files: ~/.taskrc * I posted about this error here: https://bbs.archlinux.org/viewtopic.php?id=130424 Steps to reproduce: # pacman -S task $ task list accept the default uncomment a theme in ~/.taskrc and re-run 'task list' |
This task depends upon
Comment by Peter Lewis (petelewis) -
Wednesday, 23 November 2011, 19:05 GMT
Thanks for pointing this out Ruben. As far as I can tell, these are hard-coded. I've raised an issue upstream: http://taskwarrior.org/issues/880