Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TI-29] timew config can't add new value #36

Closed
taskwarrior opened this issue Feb 11, 2018 · 3 comments
Closed

[TI-29] timew config can't add new value #36

taskwarrior opened this issue Feb 11, 2018 · 3 comments
Milestone

Comments

@taskwarrior
Copy link

@taskwarrior taskwarrior commented Feb 11, 2018

Yury Vidineev on 2016-08-01T21:21:12Z says:

If there are no such option in config 'timew config' doesn't try to add it (as opposite and expected: 'task config' can do that ).
For example:
My config file is very simple:
$ cat ~/.timewarrior/timewarrior.cfg
import /usr/local/share/doc/timew/doc/holidays/holidays.en-US

I'm trying to add option:
$ timew config reports.day.lines 4
No changes made.

Is it expected behavior? I expected something like this:

$ task config reports.day.lines 4
Are you sure you want to add 'reports.day.lines' with a value of '4'? (yes/no)

P.S. Sorry for my English

@taskwarrior taskwarrior added this to the 1.1.0 milestone Feb 11, 2018
@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 11, 2018

Migrated metadata:

Created: 2016-08-01T21:21:12Z
Modified: 2017-03-09T20:37:05Z

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 11, 2018

Paul Beckingham on 2016-08-01T22:38:51Z says:

Good catch. Thanks! Your English is perfect.

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 11, 2018

Paul Beckingham on 2016-08-16T20:24:54Z says:

As a workaround manually edit your ~/.timewarrior/timewarrior.cfg file, while this is being fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant