"While surfing the other night, I ran across a nice Emacs Lisp function for using Google to do context-sensitive help from inside Emacs.I liked how simple it was, and had always been curious about writing some Emacs lisp code (my .emacs file is a random collection of snippets I egregiously pilfered from various locations), so I thought I would enhance the solution by making it aware of what major-

If you've ever had that sick realization that you made a mistake immediately after emptying your Trash or deleting a file with Shift-Del, then Magic Rescue may be the cure you're looking for. Magic Rescue searches block devices for particular file types, then restores them to a designated directory where you can sort through them.

"While I’m talking about Ruby in Emacs, here’s a handy emacs function I wrote way back when..."

"I've been reading lots of blogs and opinions about emacs the last few days. What strikes me is all of these people who brag about how large their .emacs files have become. So let me make this very clear: If your .emacs file is longer than a page YOU ARE DOING IT WRONG. Why?

The .desktop file fills two primary functions: first, it informs the desktop environment how the file is to be handled by the desktop environment with regard to menu placement, display, environmental variables, and similar. In this function, it resides globally in /usr/share/applications/ and for specific users in $HOME/.local/applications.

"Here's a handy shortcut that toggles between the W3M web browser and other buffers you're working on. I use it to quickly switch between code and documentation (or your favorite timewasting site, as it also makes a handy boss key).

Define the function by adding the following code to your ~/.emacs: ..."

A small but useful HTML function for emacs text editor. An elisp function that, when invoked with a key combination, asks the user for the root of an HTML pair (such as 'em' or 'strong' or 'blockquote'), and then wraps the selected text or the word the cursor (point) is on in the code.

A U.S. Department of Homeland Security-sponsored project has not only discovered that the quality of open source software code has improved significantly over the past two years, it has debunked a widely held assumption that longer function strings within source code are associated with an increased number of code defects.

"... if for example you have two windows in your application and both of them have a file menu, rather than having the file menu code in both of the windows, you can define an overlay and then share this one file between both windows. This centralizes the code for the file menu and makes updating/extending the menu much easier because code changes are only required in one place..."