Ville Skyttä

Hi @kangasta ;) It's annoyingly difficult in bash. A cheap generic way is to fake the completions to be filenames. That does take care of the escaping, but it's obviously...

While I see how this would be useful, I'm not aware of a way powerline-go could do this on its own, as ssh doesn't send the alias you were using...

Not natively I think. But via a plugin that does what the git-prompt.sh shell [function responsible for that segment](https://github.com/mloskot/wsl-config/blob/a5263bda4dbf59278a2c75f2d5f9876a0487c992/git/.git-prompt.sh#L104) does and outputs it appropriately it should be doable; more info...

Reproduces at least on Ubuntu 20.04 too. I'd be interested to hear about a fix/workaround as well.

I don't think an empty method body is an appropriate way to specify an abstract method. Raising `NotImplementedError`, or marking it up with one of the [`@abc.abstract*`](https://docs.python.org/3/library/abc.html#abc.abstractmethod) decorators would be.

I think I'm in disagreement; the same argument could be used to justify disabling pretty much every pylint check. If people are annoyed by pylint starting to warn in the...

I do agree such cases likely exist. But considering the mentioned "use `pass` to indicate worrying about implementation later" workflow, there's no way pylint can know if it's an instance...

Thanks for considering this. Not using continuation is the obvious choice where applicable, but I have a bunch of cases in bash-completion with quite a few items in them and...

Cool. I think the same could be applied to combining multiple `(( ... )) ||/&& (( ... ))`.

Please note that we do _not_ simplify `${parameter:-default}` to `${parameter-default}` unless `default` is literal null, i.e. the empty string. In other words, only `${parameter:-}` gets simplified to `${parameter-}`. For other...