w3m renders HTML tables better. Or at least it used to, when I was setting up my mailcap a long time ago.

For interactive terminal web browsing I prefer links/elinks (again, compared to lynx/w3m a long time ago).

I miss the world clock too :(

I wonder how hard it would be to write an extension.

There's a switch to turn that off in gnome-tweak-tool.

Which tab? I can't seem to find this.

You get split Nautilus windows in GNOME the same way you get split anything windows: tile the window to the left (Super+Left or drag window until mouse touches the left screen edge), open new Nautilus window, tile it to the right (Super+Right or draw window until mouse touches the right screen edge). Presto.

Instructions to split a window in KDE.

   click split

You need to wrap the escapes in \[ \] to tell bash (actually readline) that these characters do not advance the cursor when printed.

I tried, for a week, got very frustrated and switched back.

The little itch that drove me crazy was command-line editing: in bash (and all readline apps) when I have

   command long/path/to/some/file

I can press Alt-Backspace to delete 'file', or I can press Ctrl-W to delete 'long/path/to/some/file'.

I tried various hacks to make zsh do the same, then gave up.

    bindkey '^[^?' backward-kill-word 

might do the trick? (possibly '^[^h' depending on what your backspace key sends. Ctrl-v <backspace> should give you something you can copy)

This makes Alt-Backspace do the same thing as Ctrl-W, which is delete-everything-until-the-next-space. I'm missing the delete-last-segment-of-the-path function.

Edit: I know I can customize the word style using $WORDCHARS, or 'autoload select-word-style'; my problem is that I'm used to having the capability to use two different word styles at once.

I'm looking through the command list in zshzle(1), and I'm a bit confused about the differences between backward-delete-word and backward-kill-word. Some short experiments I did failed to notice any differences (foo/bar/baz M-x backward-delete-word deletes foo/bar/baz). There's also vi-backward-kill-word which deletes 'baz', then '/', then 'bar', then '/', then 'foo'. I want a key to delete 'baz', then 'bar/', then 'foo', and I've no idea how to get it...

Hrmm. It works as you want for me, but there may be some other config item I've set.

The other alternative is to try:

    autoload -U select-word-type
    select-word-type bash

which should override C-w to do what you want. I haven't looked at it enough to see if you can get both behaviours simultaneously though (and it requires a fairly recent zsh iirc)

Personally I do not use virtualenv activation. Instead I prefer to explicitly launch Python and/or scripts with bin/python, bin/scriptname etc., either with my current working directory in the virtualenv, or by creating a symlink ./bin -> .virtualenv/bin in the project root.

I added a newline (\n) to the beginning of my prompt. This way I never lose program output -- and also it's easier to see where previous commands begin and end in the scrollback buffer.

You also get tons of blank lines, right? That would annoy the heck out of me.

My prompt is five lines tall, including three blank lines. I did that, along with some bright green coloring, to make the prompt easier to spot as I rapidly scroll up through a mountain of output from my last command.

zsh prompt:

PROMPT='

%{$prompt_default_color%} %~ %* %{${fg[$prompt_user]}%}%n%{$prompt_default_color%}@%{${fg[$prompt_host]}%}%M%{$prompt_default_color%} ${vcs_info_msg_0_}_

$ %{${fg[default]}%}'

You can't really do sums of top columns, because some memory is shared and you'll end up double-counting it.

And you can't just subtract the shared memory numbers, because different sets of pages are shared between different sets of processes, and top doesn't give enough information to figure out what's actually happening where.

Running the pmaps tool on all pids and summing the Pss number is perhaps the closest you can get to the actual memory use.

The ongoing efforts of the MemShrink project keep finding memory leaks -- usually in Firefox addons. You can read more about it at http://blog.mozilla.com/nnethercote/category/memshrink/