Shell | Thiago Bellini's homepage

28Mar/120

Gnome-shell Notifications Alert Extension

If there is anything that I dislike on gnome-shell are the notifications...wait, not the notifications itself, I really like the whole bottom hot corner concept and stuff. But it's very easy for me, specially at my work that I use dual monitors, to miss an im message that way.

I then started to search for a shell extension that provides something to alert me of the existence of an unread notification. I found the Pidgin Persistent Notification's concept very good and decided to try to do a generic one (since it's pidgin specific). This is the result:

2ce634507b438acb5c35a3d40adf4e08 Gnome shell Notifications Alert Extension

Without unread notifications / With unread notifications

It supports any shell version >= 3.2. You can download it on extensions.gnome at the link: Gnome-Shell Notifications Alert

The source code is on github <https://github.com/hackedbellini/Gnome-Shell-Notifications-Alert> and licensed at GPLv2. Fell free to fork it! Just don't forget to send me a pull request, so I can merge your improvements into the official code ;D

Tagged as: alert, extension, gnome, gnome-shell, notification, notifications, shell No Comments

20Oct/100

A simple script to help with simple “Test Cases”

Just here to share a simple script I wrote to help with some test cases on university.

What it does:

1- It takes all ".in" files it finds recursively on the folder and show how much time your algorithm takes to process each one.

2- For each ".in" file, it tries to find another one with the same name but with the ".out" extension. If it finds, it'll diff both that file and the output of the ".in" file and show if your algorithm is correct. If not, it shows the diff.

The script:

Download it at: http://gist.github.com/631593. Name it as you wish! (In the explanations bellow I'll assume the default name "TestCases")

How to use:

You can put the script anywhere and call it using it's absolute/relative path. If you want to call it just by it's name, make sure it's on your $PATH. To do so, add this to the end of your .bashrc:

export PATH="PATH/TO/SCRIPT":"${PATH}"

Make sure the ".in" and ".out" (if any) files are in the same folder (or in a sub-folder) of the executable you will test. Lets suppose the executable is called "EXECUTABLE" and you are on it's working directory...you can run the script like this: