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

omni uses default config file if specified config file does not exist #32

Closed
tcmitchell opened this issue May 18, 2015 · 1 comment
Closed
Assignees
Labels
Milestone

Comments

@tcmitchell
Copy link
Member

If a config file is specified by the -c option and it does not exist, omni does not report any warning or error. Instead it silently falls back to one of the default locations.

If the user specifies a config file that does not exist it should report the issue to the user so that it can be corrected. In this case, omni should probably exit rather than use a config file other than the one specified on the command line.

Imported from trac ticket #32, created by tmitchel on 10-28-2010 at 11:44, last modified: 11-09-2010 at 18:23

@tcmitchell tcmitchell added this to the 1.3 milestone May 18, 2015
@seledwards
Copy link
Contributor

commit 7c7876e0870339994917c6182dbda1939f67de76
Author: Sarah Edwards sedwards@localhost.localdomain
Date: Tue Nov 9 00:31:22 2010 -0500

Fix for Trac #32.

If configfile defined in command line does not exist, then exit with an error message.

Summary of changes:
src/omni.py | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)

Trac comment by sedwards (github user: seledwards) on 11-09-2010 at 18:23

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

No branches or pull requests

2 participants