Taskwarrior - new task, old .taskrc

new task, old .taskrc

when a new version of task is installed, it doesn't mess with my existing .taskrc, which is good behavior.

on the other hand, the taskrc has expanded significantly since my personal configuration file was created, so that many of the new variables that would be found in a freshly created .taskrc are not represented. Yes, I could study the man page, and add those new elements, but I think I would rather start with a fresh rc and re-make my changes.

plus, I'd like an easy way to see the defaults.

In order to do this, should I rename .taskrc and re-compile ?
(./configure, make, make install)

Replies

RE: new task, old .taskrc - Added by John Florian 156 days ago

David,

Here's what I do and is a method blessed by Paul long ago.

First, set aside your current taskrc

$ mv ~/.taskrc{,-good}

Now do a simple task listing which will prompt task to generate you a new default.

$ task list
A configuration file could not be found in /home/YOU

Would you like a sample /home/YOU/.taskrc created, so task can proceed? (y/n) y

Now you have a shiny brand new default appropriate for your new version of task. Use you favorite merge tool to bring across the things you want from your old rc into the new rc. I prefer to do something like:

$ gvimdiff ~/.taskrc{,-good}

RE: new task, old .taskrc - Added by David Patrick 156 days ago

an incredibly helpful and educational answer, John!

easy peasy !

RE: new task, old .taskrc - Added by Federico Hernandez 155 days ago

Another way would be to run

[ultrafredde@cottonwood ~]$ task rc:newconfigfile
A configuration file could not be found in .

Would you like a sample newconfigfile created, so task can proceed? (y/n) y
Using alternate .taskrc file newconfigfile
[task list rc:newconfigfile]
Using alternate .taskrc file newconfigfile

Then the file newconfigfile contains all new entries which can be merged into your current existing configuration file.

(I think Paul has described it like this in the FAQ.)