Grégoire Détrez

I made a workaround by writing my own branch "getter": ```py def get_submodule_branch(submodule): _c_branch = pygit2.C.git_submodule_branch(submodule._subm) if _c_branch == pygit2.ffi.NULL: return None return pygit2.ffi.string(_c_branch).decode('utf-8') ```

I've played a bit more with ambiguous options, there are similar problems with short options: ``` Usage: foo -f ARG ``` ``` sh $ foo -f bar fromList [(ShortOption 'f',Value...

After a bit more investigation, I now believe this is the same issue as #9: bits of the "old" config remain when storing the modified config. And if I switch...

Hi @JMSwag. Thanks for your answer. I understand that, if you re-generate key.gz then the old key is not included in it anymore. But I'm not really sure that solves...

Thanks @JMSwag. Yes, we started looking at TUF for our use case. We'll probably go this way although it is more complex and you need to bring your own update...

I just tried @StackOverflowExcept1on's workaround, and it seems to fix the `Maximized` issue for me :tada:

@fizyk from the error message, it looks like it's `erlexec` that complains for `HOME`. I'm not sure why either. I run my tests on ubuntu, more specifically in a ubuntu...