Great tutorial... I too was annoying the Ayche Eee Double Hockey Sticks out of my cube farm cohorts... what can I say, I do HAVE fat fingers.
Thanks again!
Great tutorial... I too was annoying the Ayche Eee Double Hockey Sticks out of my cube farm cohorts... what can I say, I do HAVE fat fingers.
Thanks again!
This didn't do anything for me other than print the 33[10etc.) on the screen when I log in. I still get the beeps.
I did. Didn't change anything. It seems logical that that's what it should be doing, doesn't it? Echo just prints back whatever comes after it...
Well, the -e option in echo enables blackslash escapes, which it seems are interpreted by the shell as commands/configuration options of some sort.
Originally Posted by smcnally
That does not seem to be the case. I tried a few variations on the command in the terminal and they all came back exactly the same:I get the sense that we're missing something here. Are you sure that that's the only line you added to .bash_profile?Code:$ echo -e "\\33[10;0]\\33[11;0]" \33[10;0]\33[11;0] $ echo "\\33[10;0]\\33[11;0]" \33[10;0]\33[11;0] $ echo "\33[10;0]\33[11;0]" \33[10;0]\33[11;0]
Are you using something other than the default shell?
What does "echo $SHELL" return?
Originally Posted by smcnally
Code:$ echo $SHELL /bin/bash
well, sorry I have no idea.
Originally Posted by smcnally
This only works in X. You can add those lines to your .xinitrc or .xsession
(not .bashrc)
Sorry, I should have clarified that orrigionally, but I didn't figure it out untill later.
Bookmarks