On 2007-06-08 23:11:58 +0200, Valentin wrote:
> Hi everybody. I've just installed lenny on my notebook and already have
> the first problemĀ :)
> It seems that when I try to pipe stdout to other programs, bash doesn't
> ignore whitespaces.
> Example:
> [EMAIL PROTECTED]
On Sat, 9 Jun 2007 09:37:31 +0800
"li sh" <[EMAIL PROTECTED]> wrote:
> Maybe there are some matters in the konsole or gnome-terminal(?) ? Try
> those commands in the real terminal ?
I had the problem in gnome-terminal and didn't test the normal
terminals. Should the problem occur again (I hope no
On 6/9/07, Bob Proulx <[EMAIL PROTECTED]> wrote:
I am actually sure that bash is working fine in general and it was
only for you in your environment that it was causing problems.
Maybe there are some matters in the konsole or gnome-terminal(?) ? Try
those commands in the real terminal ?
--
li
Valentin wrote:
> I'll now try stuff like reinstalling bash or compiling it myself,
> getting newer versions etc. Perhaps it'll work. :)
I am actually sure that bash is working fine in general and it was
only for you in your environment that it was causing problems.
Because otherwise if bash real
Huh. I don't know what I did, but it seems that somewhere I did
something right (tried everything I said and dpkg-reconfigure...)
Well, at least I now have bash 3.2
--Valentin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thanks for the suggestions
> That is very strange. Did an IFS (input field separator) variable get
> set? First I would verify that value. The following is one way:
>
> $ printf "$IFS" | od -tx1 -c
> 000 20 09 0a
>\t \n
That's what it says for me:
[EMAIL PROTECTED]:~
Valentin wrote:
> It seems that when I try to pipe stdout to other programs, bash doesn't
> ignore whitespaces.
Wow. That would make doing anything very hard.
> Example:
> [EMAIL PROTECTED]:~$ dmesg |grep foo
> [EMAIL PROTECTED]:~$ dmesg | grep foo
> bash: grep: comm
Hi everybody. I've just installed lenny on my notebook and already have
the first problemĀ :)
It seems that when I try to pipe stdout to other programs, bash doesn't
ignore whitespaces.
Example:
[EMAIL PROTECTED]:~$ dmesg |grep foo
[EMAIL PROTECTED]:~$ dmesg | grep foo
bash: grep: c
8 matches
Mail list logo