maxrossello

Furthermore, I found out that (at least on Ubuntu 18.04) the working installation as a user is to run: _activate-global-python-argcomplete --dest=- >> .bash_completion_ First, the _~/.bash_completion.d/_ folder is not considered...

Thanks @evanunderscore for your response! Maybe it's argparse's problem, but note that the misinterpretation arose from the fact that using ~ with a space does work: _$ activate-global-python-argcomplete --dest ~/.local/share/bash-completion/completions...

> @evanunderscore thanks for tracking that down, we should just use https://docs.python.org/3.8/library/os.path.html#os.path.expanduser - we could even use this shorthand: `parser.add_argument(..., type=os.path.expanduser)` great!

> > The following link provides a comprehensive review of your options: https://serverfault.com/a/831184 > > It looks like you need bash-completion >= version 2.9 for `~/.bash_completion.d` to work. Well, no....

So far my solution has been to append to ~/.bash_completion, not to delete any existing content `activate-global-python-argcomplete --dest=- >> ~/.bash_completion` I believe that this could first be used in docs,...

So, what is an equivalent syntax we can use instead?

Any plan to fix this in Linux? It is very uncomfortable to use the right-click menu for each single step and it is a very common situation for me. Thanks

I agree with you, that was also my understanding from the times of Kernigan and Ritchie. Nevertheless, modern compilers seem not to trust the developer and require an explicit cast,...

After a bit of searching, looks like it depends from the fact that I am compiling C++

yes @jktjkt actually I was basically doing the same in origin as a workaround. The problem with the proposal I envisioned is that casting the left side of the assignment...