Well, I switched from GtkTextView’s to GtkHTML’s for the tweets and popup. This way it’ll handle hyperlinks for me. I was getting close to figuring out how to figure out which word someone clicked on in a GtkTextView, but this was way easier.
Since now hyper linking works, sending updates works, the reply/retweet/direct buttons work, and the libnotify plugin works… I’ve stuck it out on code.google.
Check out the project and download it to give it a try.
I became a git fanatic quickly after hearing Linus speak. I had been using Subversion for only a few weeks when I saw the video — after using CVS for years. Not being all that impressed with Subversion, I was thirsty for something more. Git has basically become the way I version any project I start, track changes to system configurations, or even keep revisions of websites I host.
Just about all Linux server distributions install a sendmail daemon that listens on 127.0.0.1 and relays email for the localhost. This is all fine and dandy if you have a handful of Linux servers, but can turn in to chaos once you get 30+ Linux servers.
(more…)
I’ve been using CVS for at least 6 years now. I switched to using Subversion maybe in the past 3 years. When I switched to Subversion from CVS, I really didn’t understand what the fuss was about. The feature-set was really quite similar and it seemed basically like a matter of personal (or political) preference. People insisted that “Subversion was better” and if you weren’t using it, it’s because you were an ignorant jerk. So I gave into the peer pressure and started using Subversion whenever possible. Admittedly, I found a few things that Subversion would do that CVS just wouldn’t. Symbolic links, for example, are one thing that Subversion can handle and track while CVS simply cannot. However, the general structure/organization for your project between the two systems of version control are pretty much identical. That is, there’s a centralized repository that every developer uses for checking out and committing code. Furthermore, any action requires some communication with the server. Branching and merging has been equally difficult in both, in my experience, so as a general rule I stay away from doing either and keep all code in the trunk of the project’s repository.
Bash Tip #1: Reverse Incremental Searching. Quickly jumping through your bash history is super easy to do if you know about reverse incremental searching. I was shocked when I found out this existed with being a Bash lover for so long and not knowing of it.
