Marcos Lazarini wrote:
Bruce Marshall wrote:
info is an abomination in my opinion. It is very non-intuitive and I'm sorry, I don't want to take the time to learn it. (if possible)
Well, how is "Ctrl-S" (for incremental search) less intuitive than "/"? It's a matter of taste in the end, and is connected to the old vi vs. emacs war.
I tried an info file just this week and had a hard time fighting my way out of it.
Try "q"... shouldn't be so hard to find ;-)
Using Konqy to read an info file isn't bad.... but doesn't work in a console session or any place where konqy isn't.
Just my $.02
Agreed! and I want to add two more cents :-)
I usually check bash manpage to remember the syntax of some shell script commands (if, case, while, etc).
As 'case' being a somewhat rare word in texts, I type: $ man bash<enter> /case<enter> nn and I reached the right section.
Using info: $ info bash look for "Basic Shell Features" look for "Shell Commands" look for "Conditional Constructs"
another way could be like that: $ info bash look for "Reserved Word Index" look for "case" (the first that will bring "Conditional Constructs" page)
I can construct examples like that, too. Try finding the syntax of "if"...
much more difficult to remember, not to mention my classification problem: 'if' should be under "Shell Builtin Commands" or "Basic Shell Features"?
Well, try the indexes than! That's what they're for. In this case the first index "Reserved Word Index" does the trick.
-- Marcos Lazarini
Kolja