As part of bug 7867 we disabled completions when the commandline contains any of the characters in COMP_WORDBREAKS. The most common ones of these characters are '=' and ':'. This means it isn't possible to complete on the following command: tl-config --eval VAR=/vsmagent/age<TAB> Our completion code currently detects the equal sign and then stops further completions.
Note that paths can contain these special characters, meaning this limitation applies when trying to tab complete such paths too. Also note that all subsequent tab completions are disabled on a command line containing these characters, not only the current sub command or option is affected.
It might be worth looking further into how the bash-completion package handles special characters. At least for the equals sign, there is special handling for it when calling the bash-completion-function _init_completion() with the s-option which triggers splitting for long options on the format "--option=argument". As far as I have seen, there is no special handling for other characters in COMP_WORDBREAKS, but you are free to add any characters you want with the n-option. (_init_completion can be found in /usr/share/bash-completion/bash_completion) See also Bug 7867 comment 63. See also https://github.com/scop/bash-completion/blob/main/README.md
Examples of options that require '=' to complete properly are: * tl-config --eval * tl-session-param --eval These two options lack a completer function as of r40972.