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.
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...
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 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.
Exactly. If you look at the sources, you'll see that the arguments are all joined into a single string with spaces, then split back into separate words using shlex.split().
So cat("filename with spaces in it") will fail, but cat("'filename with spaces in it') ought to succeed.
It's a neat experiment, but using this module in production would not be a great idea.
As an example: I was playing Myst, uh, IV? And there was this puzzle that required me to find a short-enough path from one kind of a spot to a different kind of a spot (you had to pick up a soap bubble with a spoon and carry it somewhere, but it would evaporate if you carried it for too long; anyway, the details don't matter).
I was making a map of the level on a piece of paper, and bungled it up (the rooms that were supposed to be adjacent appeared on two completely opposite sides of the paper or something like that). The obvious next step was to write a Python script to take a description of the map (room X: exit north leads to room Y, exit south leads to room Z, etc.) and produce a map (in ASCII art; I didn't want to spend too much time on superfluous graphics).
It was more exciting to write that script and see the map it generated than it was to play the game itself.
For interactive terminal web browsing I prefer links/elinks (again, compared to lynx/w3m a long time ago).