Merge lp:~davidmhewitt/granite/fix-commandline-args into lp:~elementary-pantheon/granite/granite
Proposed by
David Hewitt
Status: | Merged |
---|---|
Approved by: | Danielle Foré |
Approved revision: | 1044 |
Merged at revision: | 1044 |
Proposed branch: | lp:~davidmhewitt/granite/fix-commandline-args |
Merge into: | lp:~elementary-pantheon/granite/granite |
Diff against target: |
11 lines (+1/-0) 1 file modified
lib/Application.vala (+1/-0) |
To merge this branch: | bzr merge lp:~davidmhewitt/granite/fix-commandline-args |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Danielle Foré | Approve | ||
Review via email: mp+322618@code.launchpad.net |
Commit message
Ignore arguments that aren't recognised by granite
Description of the change
Currently, when granite encounters a command line argument it doesn't recognise (i.e. something that's not -a (about dialog) or -d (debug mode), it stops parsing and passes all arguments (including -a and -d) to the application to handle.
Because the application probably doesn't know about the two granite specific arguments, these are often unrecognised, see: https:/
If we add the line in this proposal, granite skips over the arguments it doesn't recognise and eats the ones it does. So granite deals with the granite specific args and the application gets the rest.
To post a comment you must log in.
I can confirm that this addresses the issue