<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>powercf</author><text>Shell programmable completion highlights how slow the OS community can be to change&amp;#x2F;improve core tools (shell, coreutils, ttys). Completion should be specified in the binary, and compatible with all shells. A similar interface could be designed for all scripting languages. It was obvious ~20 years ago that it makes no sense for each shell to specify their own completion system, and yet here we still are.</text><parent_chain></parent_chain></comment><story><title>Creating a bash completion script</title><url>https://iridakos.com/tutorials/2018/03/01/bash-programmable-completion-tutorial</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>cellularmitosis</author><text>I noticed a while back that Debian 9 introduced some strange breakage with bash completion.  Previously, if you were typing &amp;#x27;dd if=&amp;#x2F;dev&amp;#x2F;...&amp;#x27; and started using tab for completion, it would behave as expected.  Under Debian 9, typing &amp;#x27;dd if=&amp;#x2F;dev&amp;#x2F;&amp;#x27; and hitting tab will turn the command into &amp;#x27;dd &amp;#x2F;dev&amp;#x2F;&amp;#x27;.&lt;p&gt;I&amp;#x27;m sure this was an oversight in the march of progress, but it sure is annoying to see a regression.</text><parent_chain></parent_chain></comment><story><title>Creating a bash completion script</title><url>https://iridakos.com/tutorials/2018/03/01/bash-programmable-completion-tutorial</url></story>