Danny Ben Shitrit

Currently, no - only 2 - but let me see if I can add more, I can see the value, just not sure it will be easy to implement.

At this point, I am not going to extend the nesting to more than the single level. I could not find a satisfactory implementation. If anyone comes up with a...

Can you provide a minimal, most basic YAML file that shows the issue?

With the default behavior of bash completions - I am unable to make it work. It indeed gets stuck after the colon. I do not know how to solve this....

> but since I am now in "personal preference"-land Actually, since I am using the non-default behavior, I agree that this is still an interesting issue as to why it...

> `$COMP_WORDBREAK` This is it. By removing colon from this variable, your use case works as expected:  ```bash _rspec_completions() { local cur=${COMP_WORDS[COMP_CWORD]} local compwords=("${COMP_WORDS[@]:1:$COMP_CWORD-1}") local compline="${compwords[*]}" # Add this...

Well - thanks for outlining the options, but I am not crazy about any of them. Keep in mind that there is also the consideration of [bashly](https://github.com/dannyben/bashly) that uses this...

> about removing the `;` I don't think keeping it will cause issues, but in general I agree. I will remove it from.... ahm... the removal.

I am closing this, as I do not see a way around it. If new information comes to light we can reopen.

A great idea, but I suspect this will be difficult to achieve without constantly configuring the selected tool due to the fact that most of the markdown files contain many...