| |||||||||||||
Glibc change exposing bugsGlibc change exposing bugsPosted Nov 12, 2010 23:39 UTC (Fri) by Wol (guest, #4433)In reply to: Glibc change exposing bugs by HelloWorld Parent article: Glibc change exposing bugs
Ah. "s" for "search".
The problem with that is if I can't articulate what I'm searching for. The number of times I've searched on what I think is the obvious search key, wasted half-an-hour or so doing it, then done a manual scroll through whatever I can find.
I then find what I'm looking for, and discover that it's called something (to me) extremely obscure, and doesn't mention my search term at all, etc etc.
Plus the fact that I'm one of those strange people who actually DOES tend to read documentation, from cover to cover, and likes to have a straight line path through it, not with redirects and jumps and god knows what all over the place. About the only place I can find information on info is in info - and if I find info repellent, how on earth am I going to find out how to use it if I have to use it to find out?
THERE is your problem with info - if you hate it because you can't find out how to use it, it's catch 22. You need to know how to use it to find out how to use it :-)
Cheers,
(Log in to post comments)
Glibc change exposing bugs Posted Nov 13, 2010 0:42 UTC (Sat) by foom (subscriber, #14868) [Link]
Oh come on, if you can't stand to use "info info" long enough to figure out that you can use "space" and "backspace" to scroll forward and backward through the document (including going to the next page automatically upon reaching the end of the current one), then I dunno what to say.
Glibc change exposing bugs Posted Nov 14, 2010 22:32 UTC (Sun) by nix (subscriber, #2304) [Link]
Well, info's handling of backspace in particular has long been buggy: it has a habit of going up to the top of the current page only, and then halting. Space has always worked, though.
|
|||||||||||||