-
Notifications
You must be signed in to change notification settings - Fork 343
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
Revise verbosity default levels and their names and abbreviations #2585
Conversation
Let -Vw (warnings+errors) become the default verbosity, and rename the various choices in a backwards compatible manner.
They are all prefaced by ERROR, WARNING, etc anyway.
Also align revised verbosity in PSL with GMT.
I just merged master branch and resolved two conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR looks good to me, but we may want more comments from @GenericMappingTools/core.
This is fine with me. |
Guys, you were too quick on merging. Sorry, it doesn't make sense to me that -V alone does nothing. If it does nothing it should not exist.
while this does (though it prints too much but that's a different issue)
|
And things are getting worst. Now this prints a lot of non-needed info, whilst before there was silence
|
I will comment and address some of these but busy with getting the proposal submittted now. |
My intent, as per @seisman's comment, was to let -V stand for -Vi. I thought I fixed that but perhaps not - will look. Yes, we also need to change the level we have assigned to some messages since some labeld WARNING that was never seen are now showed by default. Many of these need to become INFORMATION. |
BTW, when I run surface -V I get tons of INFORMATION statements. Surely you just too? |
Yes, sure. -V silence. -Vi flooding |
This is what I have:
|
Yes, I can reproduce that but try this with the attached file
|
I also got a long message:
|
Ah, found something
prints it all |
Hm, so gmt surface vs surface (bad old-school shorthand, shame on you) ? |
Weird, why is that making a difference?
then it works again. |
Very odd behavior. |
Description of proposed changes
See issue #2346 for context. This PR does several things: