-
Arnaud Rebillout authored
This is how it should have been done from the beginning. The setting 'reuse-container' is part of the YAML file, and shouldn't be needed on the command-line. For example, for kaboxed Firefox, we don't want to create a new Firefox instance every time we open a new web page. Instead we want to reuse the existing Firefox container instance, and open a new tab. That's why we set "reuse_container" in the YAML file. And from this point, we don't want user to ask themselves "Should I run with --reuse-container or not?". Nope, the developer who packaged Firefox for Kaboxer already answered this question. The decision is not in the hands of the user. With all of that being said, so what does this commit do? * 'kaboxer run' now queries the YAML file to know whether it should reuse an existing container. * the generated desktop files and cli helpers don't set the argument '--reuse-container' on the command line anymore, which allows for a nic...