Gmail bug :D

This is a small bug in Gmail. I don’t know if it’s included in the documentation. I like the way search in Google works. It’s far better than yahoo. I like Gmail’s label too. I wanted to create a label by the name “important”. Shocking! I wasn’t able to create!!! I clicked a mail and then said add new label. I entered important and the label disappeared. I tried this many times, and by mistake I typed importanta. This time the label appeared. I was wondering what was wrong. Then I moved to “edit labels” and added a label. When I gave the name as important it displayed “not valid”.. Funny thing: ) )

Russel Dominique Peters

This blog is about Russel, a guy of Indian origin, born and brought up in Canada. He is a famous stand-up comedian out there. He tours around the world and has made lot of business. To get more info about this guy, refer wiki. All his works parody one race or the other. When I saw him first I felt he might be offending, then I started liking some of his works.

Here is a comedy that I liked.

Gmail Attachments

Gmail is against sending .exe files in attachments. It also discards script files even if they are compressed. The only well known option is to rename it using a different extension. This is a not an elegant solution but it works.

This is my recent experience with gmail attachments. This incident bugged me up. The mistake I made was I renamed it using .txt extension. So what’s the problem? I had several script files(tcsh) and source files in a tarball. I had to send the tarball to the linux box at college. It was created in linux but I was mailing from windows. Don’t ask me why I didn’t mail from linux. It was for some reason. You could assume I was in windows when the need came and I had the tarball in a fat partition. I renamed it with “.txt” and sent the file. After the download-rename procedure and untarring it, my scripts weren’t working. When I copied the contents of the script to another file, character by character, it worked!! It sounded as though the editor was buggy :P. The interpreter showed that the first line contained the error. I knew it didn’t have any logical or syntax errors since it was working in my system. Usually ascii files add problems when they are moved from one os to another due to line separators (windows uses \r\n and linux uses \n). But this can’t be the problem because both of the systems were using linux. Since there couldn’t be any other reason I tried replacing all line separators using a program and the scripts worked.

Phew! I found out. This could be the possible reason. It was gmail. When I attached the tarball (fake txt file), gmail allowed it because it wasn’t an executable file. But since a text file with line separators of linux and I was mailing from a windows box, it replaced all “\n” by “\r\n”. That’s why my scripts weren’t working. I am still sceptical about this. Although it’s not likely there might have been another reason: Windows automatically converting text files to its convention.

After this incident I used software specific extensions such as(.doc) which cannot be manipulated by gmail. It works!

I am back ;)

Hi ppl, It has been long since I made a post. It was because I was little bit busy;). This post is to say ‘I am back :D’