GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-06-26 10:54:26 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Merge pull request #2543 from sebu06/getFromContext

Browse source 
Allow overriding configuration variables per context
This commit is contained in:
Tomas Babej 2021-08-29 00:00:10 -04:00 • committed by GitHub
commit 7a9c8eaf4a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
ChangeLog
View file

@ -36,6 +36,8 @@
Thanks to Beka, Max Rossmannek. Thanks to Beka, Max Rossmannek.
- TW #2101 Numeric UDA values above 2,147,483,647 overflow without warning - TW #2101 Numeric UDA values above 2,147,483,647 overflow without warning
Thanks to Adam Monsen. Thanks to Adam Monsen.
- TW #2136 Configuration options can be overwritten for current context
Thanks to Sebastian Uharek
- TW #2208 Feature: added coloring of dates with scheduled tasks to calendar - TW #2208 Feature: added coloring of dates with scheduled tasks to calendar
Thanks to Sebastian Uharek Thanks to Sebastian Uharek
- TW #2247 Configuration override rc.verbose:off not respected - TW #2247 Configuration override rc.verbose:off not respected
@ -99,6 +101,7 @@
Thanks to bharatvaj. Thanks to bharatvaj.
- TW #2581 Config entry with a trailing comment cannot be modified - TW #2581 Config entry with a trailing comment cannot be modified
------ current release --------------------------- ------ current release ---------------------------
2.5.3 (2021-01-05) - 2f47226f91f0b02f7617912175274d9eed85924f 2.5.3 (2021-01-05) - 2f47226f91f0b02f7617912175274d9eed85924f

5
doc/man/task.1.in
View file

@ -1322,6 +1322,11 @@ the user intention here, and instead, the user is expected to set the
Note how read and write contexts differ for context "family", while for context Note how read and write contexts differ for context "family", while for context
"home" they stay the same. "home" they stay the same.
In addition, every configuration parameter can be overridden for the current
context, by specifying context.<name>.rc.<parameter>. For example, if the default
command for the family context should be displaying the family_report:
$ task config context.family.rc.default.command family_report
.SH COMMAND ABBREVIATION .SH COMMAND ABBREVIATION
All Taskwarrior commands may be abbreviated as long as a unique prefix is used, All Taskwarrior commands may be abbreviated as long as a unique prefix is used,

10
doc/man/taskrc.5.in
View file

@ -1480,9 +1480,15 @@ Stores the value of the currently active context.
.RE .RE
.TP .TP
.B context.<name>=<filter> .B context.<name>.<type>=<filter>
.RS .RS
Stores the definition of the context with the name <name>. Stores the definition of the context for type <type> with the name <name>. The
type can either be read, write or rc. For details of the read and write types,
please see the task(1) man page. The rc type allows to override any configuration
parameter for the current context, e.g. if the default command for the context
home should be changed to home_report, the following statement could be added:
context.home.rc.default.command=home_report
.RE .RE
.SS SYNC .SS SYNC

2
src/libshared

@ -1 +1 @@
Subproject commit 591fa58f9c684e22a3a55dbf71bdd00c25ceb28d Subproject commit fb7e7dcffd397d214f2e71f3ff5de27ac907774f