Mechanical

Having Fun With Colleagues

I've recently entered the following curious command on my computer:

PS1='\[\033[01;32m\]api_cleanup\[\033[00m\] $ '

This makes my command prompt look like this:

 api_cleanup $                 

So why would I do that? Well, the prompt on my computer usually shows the current directory name and that name, when I'm developing new code, is the name of the current branch (copy of our code base) that I'm working on. When I asked my colleague Richard what branch name I should give our current work, he said "name it anything you want".

Heh.

So when he comes back from out meeting, he'll assume that the current branch is named api_cleanup. Had I not changed the prompt, when he came back and started pair programming with me, he would have seen this:

 richard_and_curtis_mud_wrestling_extravaganza $                 

It's going to be fun when it's time to check in the code. I'm such a geek.

  • Current Mood: amused amused
  • Current Music: Sigue Sigue Sputnik | Massive Retaliation
Tags: , ,
Which OS are you using?

On Windaft I usually use SET PROMPT= to change the prompt. (The same works under OS/2. I've never had to do anything about the prompt on OS X, though)

That explains it...

I still haven't gotten my SUN machines(A SparcStation 5 and an UltraSparc 5) to work, yet, so... no experience with that..
(Haven't had much reason to tinker in a shell on any of my Macs)

It is fun to play around with that kind of stuff, though...

Back when the office used DOS/Win3.1 and Lan Manager the logon-scripts were set to call a batch-file with the same name as the PC if it existed on the server.
It was fun to edit it so that the prompt ended up black-on-black, or always said 'C:\Windows>' no matter how many CD commands they used...
I only did those pranks to people who were also in IT, or pretended that they knew everything about PCs...

I mostly stopped with that kind of pranks, though, after I installed an OS/2 v2.0 Program Manager lookalike shell on Windows on one of my colleagues machines, and he spent most of the day trying to fix it...
(He was a real dork, who would spend the day on the net or browsing books to solve a problem after I had told him how it should be done, so he kind of deserved it)
Lols, I have a question for you. I'm taking an "Intro to C" this term. Our textbook is "C programming a modern approach". Do you have any commendations for study guides, companion pieces, or further self learning?
No worries, I'll probably just spend some time browsing Powell's technical books, I've needed an excuse anyways.