Re: Fwd: Problem with bash completion
Chris F.A. Johnson wrote: >> bash-3.2$ ./x/ < tab after x now adds slash >> >> Once the shell starts doing this, it keeps doing it. Restarting bash >> solves the problem. > >I don't see that problem, and I'm using the same version of >bash. I can reproduce it, so it's not just his imagination :) J.
Re: problems with 'read'ing from a pipe
Ok, so maybe I should have just 'read the manual' ;) But it still confuses me somewhat, since AT&T's kornshell behaves differently.. I just downloaded the latest available version for Linux from the url mentioned below, and it does work in AT&T's ksh as I expected... http://www.research.att.com/sw/download/ But I guess that you would consider that a bug in ksh ? ;) Regards, John Smith On Sat, Mar 15, 2008 at 4:09 AM, Paul Jarc <[EMAIL PROTECTED]> wrote: > "John Smith" <[EMAIL PROTECTED]> wrote: > > echo foo | read VAR > > echo $VAR > > See entry E4 in the bash FAQ: > http://tiswww.case.edu/php/chet/bash/FAQ > > > paul >
Re: problems with 'read'ing from a pipe
John Smith wrote: > Ok, so maybe I should have just 'read the manual' > ;) > > But it still confuses me somewhat, since AT&T's kornshell behaves > differently.. I just downloaded the latest available version for Linux > from the url mentioned below, and it does work in AT&T's ksh as I > expected... > > > http://www.research.att.com/sw/download/ > > But I guess that you would consider that a bug in ksh ? > ;) KSH simply works different. I don't exactly know if it makes sense for you to transform the knowledge about technical details from on eshell to the other. J.
Re: problems with 'read'ing from a pipe
"John Smith" <[EMAIL PROTECTED]> writes: > But I guess that you would consider that a bug in ksh ? POSIX allows both behaviours. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
