...more recent posts
Working on web feeds yesterday and today. This is really picky stuff. Very easy to make malformed xml. But I think I have all the main problems worked out.
But riddle me this - why does a link like this:
http://example.com/foo/bar/#123
not work in my feed reader (NetNewsWire), but this one does:
http://example.com/foo/bar#123
The first formation makes more sense to me since the 123 anchor is really attached to the implied index.html that would come after .../bar/ (i.e., .../bar/index.html#123 not /barindex.html#123) Neither way throws a parse error, but the first way just doesn't work as a link (I can click it, but it won't open in my browser,) while the second way works. Strange.
This tip from a digg discussion just made me 12% more efficient when working in the bash shell:
...note that the most efficent way to search your history is to hit Ctrl R and type the start of the command. It will autocomplete as soon as there's a match to a history entry, then you just hit enter...The internets are just full of useful information.
(bash is a unix shell. A shell session is where you interact with the command line - sort of like dropping into DOS and getting a C> from Windows, except better.)