END; require_once "include/calendar.php"; require_once "include/planner-include.php"; require_once "include/header.inc.php"; ?>


B1CBorrow recode-region: Post from Magnus Henochon nntp+news.individual.net:gnu.emacs.sources (nil)


23. xtla and Gnus

Categories: 2005.06.02:4 emacs#14 EmacsTips:23 -- Permalink, Comment form

There is a feature in xtla.el to send/review patches via gnus.

To set it up, you need the following lines for your .emacs:

(setq tla-apply-patch-mapping
      '(((nil "planner" nil  nil nil) "~/work/planner-dev/")))
Replace ~/work/planner-dev/ with your planner working directory

The patches are sent as .tar.gz files.

When you receive such a patch (I will send one soon), You can hit
K t v to view the patch
K t a to apply the patch

I can even provide a log message in the mail. You can insert the log message via C-c C-p in the tla-log-edit buffer.

E-Mail from Stefan Reichör

その限られた性能のために私はコンピユーターに幻滅を感じている。 Its limited capability has disenchanted me with computer.

Permalink, Comment form -- Back to top

22. Managing my mail

Categories: EmacsTips:22 tips emacs -- Permalink, Comment form

I use Gnus, one of the many mail/news clients available for Emacs. The following features help me manage the volume of mail I get each day.

Mail splitting

Yes, yes, the Gmail way is to keep everything in one folder and then use searches to filter your messages. Still, I like being able to glance at my screen and see 2 personal messages and 3 planner-related messages.

Topics and group hiding

I use Gnus topics to divide my mail into folders and subfolders. Mail groups are hidden unless they have mail. Some groups like mail.misc and mail.planner are generally useful, so I keep them visible even if they don't have unread mail.


Gnus allows you to automatically score threads and messages up and down based on various criteria. You can set it to completely hide boring messages, show them in a different color, show interesting messages in a different color, etc.

On most mailing lists and newsgroups, I don't bother reading message bodies. I just scan through subjects, hitting k to kill entire threads I don't find interesting. Gnus remembers what threads I've killed, marks them as read, and scores them down automatically. It also scores up messages containing certain keywords, replies to my posts, and threads I found interesting.

Integration with my contacts

I put interesting people in my BBDB contact database. Gnus indicates messages from them with a little + beside their name in the message summary. If someone I know is interested in a thread, I might find it interesting as well.

Hiding and article washing

I've set Gnus up to hide quoted text. This makes browsing through threads much easier because I can concentrate only on the the new parts. I can hit a few keys to expose sections of the quoted text if the replies aren't immediately obvious from the context.

I can also set it up to remove ads at the bottom of messages, particularly long signatures, To: lines with more than N recipients, that sort of thing. I can tell it to strip out HTML, too.

Displaying parent article

Sometimes I'll jump into the middle of a thread. I can use ^ to get to the parent message.


I use swish++ to index and search through my personal and planner-related mail.

Planner hyperlinks

Most of my tasks come in through e-mail. Planner lets me keep track of my TODOs easily by automatically hyperlinking to the mail message I'm looking at when I create a task. Dealing with a few items on my TODO list is much easier than going through a large inbox! =)

Permalink, Comment form -- Back to top

21. Emacs for Authors

Categories: emacs EmacsTips:21 -- Permalink, Comment form


A book writer has written a guide on how to use Emacs in lieu of mainstream word processors. Check it out!

Post from R. Wood on comp.emacs

Permalink, Comment form -- Back to top

20. two-mode-mode: Multiple modes in one Emacs buffer

Categories: EmacsTips:20 emacs -- Permalink, Comment form

two-mode-mode allows you to switch between two major modes in a single buffer. You can find it at http://www.dedasys.com/freesoftware/files/two-mode-mode.el If you need to deal with more modes, check out Multiple Major Modes at http://mmm-mode.sourceforge.net .

Permalink, Comment form -- Back to top

20. One #emacs day - 0. 2005.01.05 and 1. 2005.01.06

Categories: [[EmacsDay#note1][EmacsDay:1]]"[[EmacsTips#note20][EmacsTips:20]] -- Permalink, Comment form

(Technically, one and a half, because this is the first entry)

Here are interesting tidbits from irc://irc.freenode.net/#emacs

Permalink, Comment form -- Back to top

18. Keeping track of time with planner-timeclock and planner-timeclock-summary

Today I discovered the immense usefulness of keeping track of time. I had converted the TODO my teammate sent me into entries in my JapanProject plan page, and before starting my work I came up with rough estimates of the time it would take me to do the tasks. I also marked which tasks I felt were best suited for my coworker so that he could get started without worrying about conflicts. I like working on little tasks first, so I estimated the time it would take me to complete each task and sorted by my estimates using the 'sort' command and some cutting and pasting.

Then the fun began. I wanted to see if I could match my estimates. Before I started working on a task, I used C-c TAB to mark it 'in progress' and start the clock. When I finished it, I used C-c C-x (planner-task-done) to mark it completed and automatically clock out. This is not yet done for cancelled tasks, so I clocked out of those manually with C-c C-o (timeclock-out). I also clocked out whenever I caught myself being distracted so that the totals wouldn't include the time I spent chatting on #emacs or checking out del.icio.us links. ;) At the end of the day, I used 'planner-timeclock-summary-show-range-filter' to show me the time elapsed for all of the tasks I'd worked on over the past two days. Here's the report for that project, edited to reflect how it looks on my screen and annotated with comments:

Timeclock summary report for 2004.12.28 - 2004.12.29

JapanProject0:23:173.6%Translate javadoc comment for Messages.java
0:33:485.3%Translate javadoc comment for LoginAction.java
1:54:0717.8%Study Struts in Japanese
0:46:087.2%Add javadoc tags for input, output and forwards
1:03:489.9%Help review code
0:04:140.7%Import todo list
0:00:370.1%2min Fix Menu Action's unnecessary code (delegated)
0:01:010.2%2min Remove unnecessary list in UserRemoveSetupAction (cancelled)
0:02:100.3%2min Remove hard-coded database path from MenuAction
0:02:460.4%30min Create a superclass for our action classes that handles initialization of database and handling of privileges - remove all privilege handling in logic classes. ...
0:07:321.2%5min Add a method that returns the validity of a user in MUserPeer.
0:08:281.3%5min Fix indentation
0:03:520.6%10min Fix UserPeer so that it doesn't get null pointer exceptions
0:04:340.7%5min Add current password field in user_modify page (cancelled)
0:21:563.4%15min Make a super class for our service classes that will receive the database connection. (cancelled)
0:06:050.9%10min Remove hard-coded constants from the Logic classes
0:10:551.7%10min Move logic from UserBean.checkPassword to UserListLogic
0:01:200.2%20min Guard against null pointer exceptions in peer classes
0:04:570.8%10min Instead of displaying uneditable data with bean:write, just disable the html:text element
0:25:033.9%10min Deploy 10:00 version
0:04:460.7%5min Separate the configuration file of database and system into another uninternationalized property file.
2:09:4820.2%1h Decide on a naming convention for localized messages and update files
0:00:070.0%20min Explain what is happening in UserModifyAction's nested ifs (pending)
1:50:2317.2%2h Write Javadoc comments in English and Japanese to explain bean structure
0:04:190.7%2h Write Javadoc comments in English and Japanese to explain peer operations (pending)
0:05:400.9%20min Make a factory class for the database (pending)

Day began: 13:03:58, Day ended: 20:51:46 Time elapsed: 31:47:48, Time clocked: 10:41:41 Time clocked ratio: 33.6%

The time record isn't perfect. I cancelled some tasks after thinking about them a little and did some tasks simultaneously. Sometimes I didn't notice that I was getting distracted, too. Still, having all of that time information neatly summarized made me realize a number of things.

First, I goof off much less when I have a nice, broken-down task list in front of me. There's just something about knowing there's a five- or ten-minute hack you can get out of the way. I found myself looking forward to getting to the next task just to see if I could make my estimate. That said, seeing a five-minute task stretch and stretch due to unforeseen problems did make me a little nervous. I should probably just make generous estimates so that I don't end up with bugs because of haste.

Second, I don't goof off as much as I thought I did, although there's still room for improvement. Yesterday's workday was 9:00 - 12:00, 1:00

  • 5:30--7.5 hours. Today was the last day of work, so cleaning and celebration interrupted my hacking at around 3:00--5 hours of work. According to my task list, 10:41/12:30 was productive work. Hmm. 1:49 hours unclocked time when I was thinking or goofing off. planner-timeclock-summary-show for today reveals that I actually clocked 5:30 today, which means the goofing off happened yesterday. That makes sense; I remember a pretty long unclocked segment recuperating from Japanese overload. (This was before we came up with the task list.)

Third, keeping track of time is way, way cool even if you don't bill anyone for your time.

Like the idea? It's easy to try out. If you use the development version of planner, just add

(require 'planner-timeclock)
(require 'planner-timeclock-summary)
to your ~/.emacs. If you want to try it out now, eval those statements in your Emacs session. After that, simply use C-c TAB to 'clock in' a task before you start working on it, and use C-c C-x (planner-task-done) to mark it completed. To see a summary of how you spent your day, check out the different functions in planner-timeclock-summary.

If you use the stable version of Planner, you can grab planner-timeclock.el and planner-timeclock-summary.el from http://sacha.sachachua.com/notebook/emacs/dev/planner/ , try out the dev version, or cherry-pick the relevant arch patches. If it works for you too, please e-mail me so that we can merge it into stable! =) (I tend to trust myself very little, seeing how I manage to screw up dev from time to time.)

Happy hacking!

17. Tracking callers of elisp functions

You can display a call graph after byte-compiling a file by adding this to your ~/.emacs:

(setq byte-compile-generate-call-tree t)
bojohan also said that list-callers.el might be interesting.

Chat with :bojohan on zelazny.freenode.net#emacs

16. More Emacs tips


From Douglas Johnston:

In case you're interested, the second part of my "Emacs retreat" is online at the blog. (It's mainly for wanna-be Emacs users, but emacs-wiki/planner figure prominently in my usage.)


E-Mail from Richi's server

15. u-color-cycle.el

Ulf Jasper's u-color-cycle.el smoothly changes the color of all text in a window or region while you stare at it, mesmerized. It reminds me of those setcolor tricks I used to do in grade school and high school. u-color-cycle.el is a cute, harmless diversion that just goes to show Emacs hackers have way too much time on their hands. ;) (This is a Good Thing.)

E-Mail from Ulf Jasper

14. Emacs, the self-documenting editor

In response to http://www.livejournal.com/~cmarguel/5405.html?nc=1 :

Miguel Arguelles wondered what was so self-documenting about Emacs. Paolo showed him the source code, but Miguel pointed out people have to type those comments in anyway. So what makes Emacs a self-documenting editor and my favorite tool?

Emacs is called a self-documenting editor because the source code to _any_ function can be found with a few keystrokes. Curious about how M-x find-file works? Use C-h f to look up the definition, follow the link in the help buffer, and get as much detail as you want. You can even use the Emacs debugger (edebug) to explore the behavior of functions. Emacs exposes its internals to an extent no other editor has even attempted.

Code? Why are we looking at code? Shouldn't we be looking at neat comments explaining how everything works? The paradigm shift here is that _code_ is often the best documentation for itself. Comments should explain usage and the background reasons for coding, but the code itself should be clear and easy to understand. Programming languages like C and Java tend to encourage short, almost cryptic identifiers. Lisp may initially seem daunting because of the parentheses, but the long identifier names and the simple structure make it easy to read even if you don't have a background in functional programming.

Not only can you look functions up, but you can also _change_ them while Emacs is running. Don't like the way save-buffer works? You can redefine it with a little Emacs Lisp programming. Want to do some pre- or post-processing? There's support for that too. Emacs is a rapid development environment for itself. That's why there are so many modules available for it. Emacs is an editor you can customize to your heart's content.

Documentation is just a few keystrokes away. All the commonly-used functions and variables have clear instructions for usage. Emacs coding style suggests having a documentation string explaining the arguments and usage for each function, and there are tools for checking compliance. Emacs also has a lot of contributed documentation on http://www.emacswiki.org and other Emacs-related sites.

Emacs doesn't hide anything from you. That's why Emacs is called a self-documenting editor. Even after trying out other editors like Eclipse and vim, I still go back to Emacs. I've tasted power, and I'm hooked.

13. Lisp code for correct coding

(setq erc-encoding-coding-alist (quote (("#lisp" . utf-8)
          ("#nihongo" . iso-2022-jp) ("#truelambda" . iso-latin-1)
          ("#bitlbee" . iso-latin-1))))

12. top-level

(when (featurep 'xemacs) (top-level))
Handy way to prevent XEmacs from interpreting the rest of your .emacs.

Chat with bojohan on zelazny.freenode.net#emacs

11. dabbrev-hover

dabbrev-hover http://gnufans.net/~deego

Tooltip-show the next completion. Hmm, that's nice.

E-Mail from D. Goel

10. Emacs on the Playstation 2

Having problems with backspace and delete on Emacs on the PS/2 Linux kit? Here's what Eric says:

  <ericvids> sachac: I knew it, it's a program-trying-to-outsmart-its-user bug.
  <ericvids> sachac: I bound backspace to delete, but I shouldn't touch delete.
             They need to be *both* delete-char.  And the old emacs was trying
             to automagically decide whether to move backward or stay in place.
  <ericvids> sachac: On the other hand, maybe I should just keyboard-translate
             that.  After all I'm just trying to prevent emacs from modifying my
Chat with ericvids on localhost#bitlbee

9. Debugging Emacs hangs

Run emacs in gdb, preferably from the src directory where you compiled emacs:

   $ cd ~/emacs-build/src
   $ gdb ./emacs
[There's a special .gdbinit file in that directory that defines handy emacs debugging commands.]

When it hangs, hit C-z or something to exit to the debugger (you can't use C-c like usual when debugging emacs, because emacs' standard .gdbinit file changes gdb's SIGINT handling to make C-g work properly on ttys).

Then look at a C backtrace ("backtrace") and lisp backtrace ("xbacktrace") to see what's up.

For more fun, do the above from another emacs session using emacs' `M-x gdb' command.

E-Mail from Miles Bader

8. Snarfing appointments from mail


Check out u-appt.el and icalendar.el .

E-Mail from Ulf Jasper

7. Emacs Learning Instruction Program

The beta of ELIP, the Emacs Learning Instruction Program, is now stable enough for wide release.

ELIP is "flashcards on steroids" and provides learning via

  • spaced interval recall (like SuperMemo)
  • Leitner "box" method
  • plain old flashcards

Modes are present for questions and answers in

  • simple form
  • ellipsis form, generated from chosen text material
  • passage memorization form (i.e., memorize the Gettysburg address).

ELIP installation requires some EMACS 'smarts' and had EDB, the EMACS Database, as a prerequisite. This is all explained in the documentation.

The distribution comes with a small Hawaiian language database, a large Spanish vocabulary database, a large Esperanto vocabulary database, an Esperanto grammar database, and the "I Have a Dream" speech for learning by memorization.

There is a small, low volume mailing list available.

ELIP is found at


and comments, bug reports, ideas and suggestions are welcome.

E-Mail from

6. back-to-indentation: jump to first non-blank character

To move over the indentation on a line, do `M-m' (`back-to-indentation'). This command, given anywhere on a line, positions point at the first nonblank character on the line.

E-Mail from iso

5. gnu.emacs.sources/tex-skak.el: a way to typeset chess moves and board diagrams in LaTeX

This is a special mode for editing LaTeX files which use the skak package.

\usepackage{skak} is a beautiful way to typeset chess moves and board diagrams in LaTeX. This file implements a special editing mode for such documents ontop of the AUC TeX and chess.el packages. Both packages are very flexible and extensible. This file can be considered glue code to unify the power of both packages.

Mirrored at ../emacs/tex-skak.el

E-Mail from Mario Lang

4. Ebook: Emacs in 24 hours

3. ff-find-other-file

ff-find-other-file lets you switch from, say, a .cpp file to an associated .h file.

E-Mail from Felix

2. Checking for unmatched parentheses

M-x check-parens

1. Really funky BBDB aliases

Categories: None -- Permalink, Comment form

Apparently, you can define a mail-alias field on multiple BBDB records, add the following elisp snippet to your .gnus

(add-hook 'message-setup-hook 'bbdb-define-all-aliases)
(add-hook 'message-setup-hook 'mail-abbrevs-setup)
and expand aliases to multiple e-mail addresses with tab.

E-Mail from Sarir Khamsi Cross-reference: 2003.11.10:2