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

new-only option must appear before keep #7

Closed
dave-kennedy opened this issue Jan 7, 2016 · 3 comments
Closed

new-only option must appear before keep #7

dave-kennedy opened this issue Jan 7, 2016 · 3 comments

Comments

@dave-kennedy
Copy link

If an account is defined with keep and new-only options, they must be specified in a certain order. For example:

account "imap" imaps server "blah" user "user" pass "pass" keep new-only

This throws an error:

~ $ fdm fetch
/home/dave/.fdm.conf: syntax error at line 6

This works though:

account "imap" imaps server "blah" user "user" pass "pass" new-only keep
@nicm
Copy link
Owner

nicm commented Jan 15, 2016

Yes... that is right.

@nicm nicm closed this as completed Jan 15, 2016
@dave-kennedy
Copy link
Author

Ok. Was this mentioned in the manual? I must have missed it. Seems kinda odd that it would matter.

@nicm
Copy link
Owner

nicm commented Jan 19, 2016

Yes keep comes after arguments:

account name [users] [disabled] type [args] [keep]

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

No branches or pull requests

2 participants