The tab-completion seems to work differently (and less desirably) in KSH than it does in BASH.
For example, the following is just not possible with tab-completion in KSH: $ grep '<tab> This results in a BEL sounded (expected) and the single-quote (apostrophe) being erased (unexpected). Even if there are no matching files (which there is not), why is the single-quote character erased? When using BASH, results are more what one would expect; namely the above results in a BEL sounded but the apostrophe character remains. The same occurs with the double-quote character. KSH erases the double-quote on completion failure while BASH retains it. It the KSH behavior some sort of feature? Also, Is there a way that tab-completion can be turned OFF entirely? Thanks for any information. David Morano [email protected] _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
