The Pensieve

XEmacs - Still resisting the dark side The other day, I had been contemplating changing to a fancier text editor. Though I do little programming now, I still find a need for a programmer's editor as I will be frequently writing simple scripts or processing csv files created by Microsoft Excel or log files. The other editor that I am familiar with is JEdit , which I had used for a brief period and have even contributed a macro . It had a good GUI, syntax highlighting for numerous programming languages and scripts, searching capability, plugin support, extensibility and so on. But, the one point it faltered was on the memory usage side. Just opening the editor took away a good 40MB of my scarce RAM. I guess it needed the memory to display those fancy icons and GUI controls. XEmacs in comparison, ends up using less than 10MB and is way faster too. Some indispensable commands Over the course of time, I have started relying on a few commands, so useful that I use them almost daily. You...

XEmacs init.el It's been almost eleven years since when I was introduced to GNU EMACS. It came in as a DOS based editor which failed to load files that were over 640k. This was followed by DPMI support which provided flaky support to open files larger than than and unreliable under Windows 3.1. I then migrated to GNU EMACS on win32 and finally settled down with XEmacs on XP. Over the years, my (X)EMACS config file has and still undergoing changes and here is the latest configuration that I maintain. Note: I am not a lisp hacker, but have basically accumulated a list of handy configuration options and snippets that were indispensable during the course of my programming career. ;; ;; Shoban's XEmacs init.el ;; ;; ---------------------------------------------------------------------- ;; load paths ;(pushnew "~/.xemacs/xemacs-packages/dmacro" load-path :test 'equal) (pushnew "~/.xemacs/xemacs-packages" load-path :test 'equal) (setq Info-directory-list ...