You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A suggestion by @linuxcaffe was made to expand the installer to a reconfiguration service/interface. For example, linuxcaffe may share a file, on Git or Instagram whatever, that specifies its setup in a format that is supported by this installer:
taskwarrior & timewarrior
These 7 hook scripts
sorting on due date
max 50 tasks
some colour settings
etc. etc.
and someone could get the link or scan the QR code to get a taste of the setup that linuxcaffe uses. (Because the reconfiguration service of this installer would change the configuration of the user towards that of linuxcaffe on the fly).
Advice was given regarding the folder structure that might be convenient for such a service.
For enabling and disabling things in the.taskrc file, it may be useful to use nested-includes. For example, the .taskrc could perhaps contain all the basic taskwarrior settings, and it could have a line include ~/.task/install/install.config. Then that install.config file I could have some settings AND a line include ~/.task/install/example-hook.config which in turn would then enable-/disable hooks (and so-on).
The text was updated successfully, but these errors were encountered:
A suggestion by @linuxcaffe was made to expand the installer to a reconfiguration service/interface. For example, linuxcaffe may share a file, on Git or Instagram whatever, that specifies its setup in a format that is supported by this installer:
and someone could get the link or scan the QR code to get a taste of the setup that linuxcaffe uses. (Because the reconfiguration service of this installer would change the configuration of the user towards that of linuxcaffe on the fly).
Advice was given regarding the folder structure that might be convenient for such a service.
For enabling and disabling things in the
.taskrc
file, it may be useful to use nested-includes. For example, the.taskrc
could perhaps contain all the basic taskwarrior settings, and it could have a lineinclude ~/.task/install/install.config
. Then thatinstall.config
file I could have some settings AND a lineinclude ~/.task/install/example-hook.config
which in turn would then enable-/disable hooks (and so-on).The text was updated successfully, but these errors were encountered: