Re: Bash command completion when not connected to a terminal

completion also showed me the completed filenames. It's a little bit nonstraightforward, but it solved the problem. Does anybody know of an easier way to do this? -- View this message in context: http://www.nabble.com/Bash-command-completion-when-not-connected-to-a-t

Re: Bash command completion when not connected to a terminal

trolled in bash? Is this just a difference between bash 3.00.16 and 3.2 (or maybe a difference between Windows bash and Solaris bash?), or do the two shells just happen to use slightly different default settings? Is there a way to configure bash to echo back each character that was sent to it's stdin? -

Re: Bash command completion when not connected to a terminal

raner <[EMAIL PROTECTED]> wrote: > The completion seems to work, but I do not receive the completed filename > from the shell's stdout. It's written to stderr, not stdout. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/l

Bash command completion when not connected to a terminal

s connected to a terminal? Or am I misunderstanding how the completion is supposed to work, and part of the work is actually done by the terminal and not by the shell? Any help is greatly appreciated! Thanks, Mirko -- View this message in context: http://www.nabble.com/Bash-command-completion-wh