Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Bash doesn't ignore whitespacesHi everybody. I've just installed lenny on my notebook and already have Does anybody have an idea what could be wrong or what I could change to --Valentin Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Bash doesn't ignore whitespaces
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:
> apo@eyecookie:~$ dmesg |grep foo
> apo@eyecookie:~$ dmesg | grep foo
> bash: grep: command not found
>
> Does anybody have an idea what could be wrong or what I could change to
> make it work again?
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
0000000 20 09 0a
\t \n
Next I would verify that 'grep' is really the grep that you think it
should be. But I assume your whitespace statement applied to all
commands.
type grep
Next I would check your $HOME/.bashrc file and $HOME/.bash_profile
files for anything that might have aliases 'grep' to something else.
Bob
--
Bash doesn't ignore whitespaces
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
> 0000000 20 09 0a
> \t \n
That's what it says for me:
apo@eyecookie:~$ printf "$IFS" | od -tx1 -c
0000000 20 09 0a
\t \n
0000003
> Next I would verify that 'grep' is really the grep that you think it
> should be. But I assume your whitespace statement applied to all
> commands.
>
> type grep
grep is /bin/grep
>
> Next I would check your $HOME/.bashrc file and $HOME/.bash_profile
> files for anything that might have aliases 'grep' to something else.
There's nothing in any of those files. Would be weird, too. After all I
only installed Debian yesterday ;)
I'll now try stuff like reinstalling bash or compiling it myself,
getting newer versions etc. Perhaps it'll work. :)
--Valentin
--
Bash doesn't ignore whitespaces
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
--
Bash doesn't ignore whitespaces
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 really were having the problem as you
described it then virtually nothing else in the system would work.
The system would not be able to boot. The system would not be able to
start your processes. You would not be able to get to a command
prompt in order to find the problems you were having in your
environment.
It would be much worse than you described and so I was sure that bash
itself was working fine.
Bob
--
Bash doesn't ignore whitespaces
On 6/9/07, Bob Proulx 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 ?
--
lish
--
Bash doesn't ignore whitespaces
On Sat, 9 Jun 2007 09:37:31 +0800
"li sh" 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 not - it's annoying),
I'll try that. But I don't think that it was gnome-terminal...
--Valentin
--
Bash doesn't ignore whitespaces
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:
> apo@eyecookie:~$ dmesg |grep foo
> apo@eyecookie:~$ dmesg | grep foo
> bash: grep: command not found
>
> Does anybody have an idea what could be wrong or what I could change to
> make it work again?
Perhaps you have typed shift-space so that you got a nbsp instead
of a normal space (this sometimes happens to me when the previous
character needs the shift key). That could also comes from the
configuration of your keyboard (application-specific or not).
--
Vincent Lefèvre - Web:
100% accessible validated (X)HTML - Blog:
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
--