How to Delete Untracked Files in a Mercurial Repository
Working around Firefox at Mozilla means that you need to get acquainted with mercurial, the version control system that rivals git and svn. Like any tool, hg (mercurial) can be difficult until you're well versed with it. And if you hg import a URL that doesn't match up with what's in the repo, you'll get a bunch of *.rej files that in your directory structure that show up every time you hg status. Gross.
If you want to start from scratch and remove all those unwanted files, there are two steps. The first step is enabling the purge extension within your ~/.hgrc file:
[extensions]
purge=
With the purge extension available, it's as easy as running hg purge to get rid of all of the unwanted files:
hg purge
With those unwanted files gone, it's easy to get back to the business of being productive with as few useless obstructions getting in your way!
![Serving Fonts from CDN]()
For maximum performance, we all know we must put our assets on CDN (another domain). Along with those assets are custom web fonts. Unfortunately custom web fonts via CDN (or any cross-domain font request) don't work in Firefox or Internet Explorer (correctly so, by spec) though...
![CSS vs. JS Animation: Which is Faster?]()
How is it possible that JavaScript-based animation has secretly always been as fast — or faster — than CSS transitions? And, how is it possible that Adobe and Google consistently release media-rich mobile sites that rival the performance of native apps?
This article serves as a point-by-point...
![Create GitHub-Style Buttons with CSS and jQuery, MooTools, or Dojo JavaScript]()
I'm what you would consider a bit of a GitHub fanboy. We all know that GitHub is the perfect place to store repositories of open source code, but I think my love of GitHub goes beyond that. GitHub seems to understand that most...
![Record Text Selections Using MooTools or jQuery AJAX]()
One technique I'm seeing more and more these days (CNNSI.com, for example) is AJAX recording of selected text. It makes sense -- if you detect users selecting the terms over and over again, you can probably assume your visitors are searching that term on Google...
