zomg, another chapter up!

Warning: include_once(): Unable to allocate memory for pool. in /var/www/sachachua.com/blog/wp-content/plugins/nextgen-gallery/pope/lib/class.component_registry.php on line 939 Warning: include_once(): Unable to allocate memory for pool. in /var/www/sachachua.com/blog/wp-content/plugins/nextgen-gallery/pope/lib/class.component_registry.php on line 939 Warning: include_once(): Unable to allocate memory for pool. in /var/www/sachachua.com/blog/wp-content/plugins/nextgen-gallery/pope/lib/class.component_registry.php on line 939

I’ve finished the first draft of Chapter 8: Taming Your Tasks. PDF ODT DOC. Whee!

The feedback I’m looking for right now is:

  • Does the chapter flow properly, or would it make better sense rearranged?
  • Does it cover all the things a basic chapter on task management should cover? (I know, the Planner thing’s a bit sparse… My original ‘budget’ for this chapter was 35 pages!)
  • Does it include at least one or things that make you go “Hmm, that’s interesting”?
  • Is it missing some of your favorite hacks or coolest features?

Fiddly bits like formatting will wait for the second pass.

If you leave your feedback as comments on this post, I’m less likely to lose it in all the mail that’s piling up in my inbox! =)

On Technorati: , , , ,

Random Emacs symbol: widget-specify-secret – Function: Replace text in FIELD with value of `:secret’, if non-nil.

  • http://pigpog.com Michael Randall

    I never did get the hang of OrgMode before, so I’ve been following along with this as you’ve been posting bits. It’s really helping.

    There may be a problem with the code section for “basic configuration for Org and Remember”, or it may just be different because of different versions – I’ve grabbed the current release of Org. Using this code with the current release, with the titles added in as they were in the blog post, doesn’t add stuff to the ‘Inbox’ section. I had to add a fifth field “Inbox” to the line containing the (2), so Remember would insert the task in the right section.

    Not sure what’s best on your question on use of CTRL- and META- instead of C- and M-. The former are more familiar to most people, but the latter are familiar to Emacs users. Readers are likely to come across the latter format when they read any other documentation, though, so avoiding tackling the issue in the book might just shift the confusion to the first time they read anything else. Using upper case for the keys does seem confusing, though – CTRL-c could only be one thing, but CTRL-C could mean CTRL-SHIFT-C.

    Anyway, time to do some sleeping now, so I’ll read more another time. It’s looking great so far – thanks for sharing the work-in-progress.

  • http://www.soton.ac.uk/~rpb Rich Boardman

    Hi Sacha,

    Nice to see someone writing a book like this and very good of you to share :)

    I had a quick read (just stumbled on your site by accident) – I was going to mention something similar to Michael. Regarding C-/Ctrl- and M-/Meta-: I would use C- and M-, as this is used pretty much everywhere else in the Emacs world, but maybe explain earlier on that C- means Ctrl and M- means Meta.

    Just my tuppence there.

Warning: require_once(): Unable to allocate memory for pool. in /var/www/sachachua.com/blog/wp-includes/template.php on line 501 Warning: require_once(): Unable to allocate memory for pool. in /var/www/sachachua.com/blog/wp-includes/template.php on line 501