Thomas Flori

interesting idea. but we would need to define somehow what happens when an option is unknown and what else could someone want to do when an option is unknown except...

so the process method catches his own exceptions and checks an option if the exception should be thrown or just rememberd? sounds good

https://github.com/Arcesilas/getopt-php/commit/ca2baca811cd43b0a95017777fe187607adedfba looks good except some namings. The comment about static methods I don't understand. There are only 3 static methods in the GetOpt class. There is no way to use...

I would recommend to have two settings: `SETTING_THROW_EXCEPTIONS` and `SETTING_STOP_ON_ERROR`. When throwing exceptions stop on error is implicit enabled. The exception from setValue has to be catched the usual way:...

Yes, stop on error without throwing exceptions is the same as catching a thrown exception. But some people might argue that the code looks very different: ```php $getOpt = createGetOpt();...

it would be helpful anyway. why to waste time running it twice when you just want different output formats of the same result? I suggest to have separate command line...

I also would like to disable that. The reason are dialogs that you move to another monitor are pushed in the background what makes it complicated to go back to...

@jtaala at least I understand now why it is not possible to change that without gnome changing something. and that means, that the main concept of paperwm is not supported...

maybe it comes from this restriction.. the cookie is not submitted anymore - I can't debug

yes, that is another solution that would allow the user to choose the implementation of collections he want to use. but I'm afraid that is not all we have to...