| |||||||||||||
Glibc change exposing bugsGlibc change exposing bugsPosted Nov 11, 2010 9:46 UTC (Thu) by mpr22 (subscriber, #60784)In reply to: Glibc change exposing bugs by HelloWorld Parent article: Glibc change exposing bugs
For large manuals, my experience is that
(Log in to post comments)
info considered harmful?
info considered harmful? Posted Nov 12, 2010 14:08 UTC (Fri) by jzbiciak (✭ supporter ✭, #5246) [Link]
Another vote for pinfo. It doesn't hate me for wanting to know something like "info" does.
Glibc change exposing bugs Posted Nov 11, 2010 22:56 UTC (Thu) by HelloWorld (guest, #56129) [Link]
Dividing manuals into chunks of a sensible size is a feature, not a bug. And if you don't like GNU info or emacs, just use something else. You can view info manuals with konqueror by typing info:<program name> into the address bar, and yelp is also capable of displaying info documents.
Glibc change exposing bugs Posted Nov 12, 2010 18:19 UTC (Fri) by sorpigal (subscriber, #36106) [Link]
I don't know about you but for anything less than ten pages I find man much easier than info for one very simple reason: It's easy to scroll through a stream of text. It's also easier to hit / and search the whole document, it's easy to not get lost, etc.. Info's problem is that info readers don't default to a man-like one-big-document, which is well known, well accepted and suitable to a terminal (which is, I imagine, where most man and info pages are consumed).
I've used pinfo and it helps some in the UI department, but I'd still use man over pinfo for almost every trivial lookup. If your goal is to completely replace man then your system needs to be a drop-in replacement from a user interaction point of view, with the advantages discoverable by users who are interested in learning them.
Glibc change exposing bugs Posted Nov 12, 2010 18:45 UTC (Fri) by foom (subscriber, #14868) [Link]
> easier to hit / and search the whole document
Not really: "info" also searches the whole document if you hit /. (although I share the general dislike for the info browser).
Glibc change exposing bugs Posted Nov 25, 2010 15:22 UTC (Thu) by Spudd86 (guest, #51683) [Link]
info's major problem is that it's interface SUCKS, there's no real 'back' command, the keybindings are just plain weird (unless you're an EMACS user...).
It'd be nice to have an info viewer that converts to HTML on the fly and uses webkit to render it.
Glibc change exposing bugs Posted Nov 25, 2010 22:13 UTC (Thu) by paulj (subscriber, #341) [Link]
Have you tried going to System -> Help? GNOME's "Yelp" supports browsing info docs - providing a web browser style GUI...
Glibc change exposing bugs Posted Nov 26, 2010 0:31 UTC (Fri) by Spudd86 (guest, #51683) [Link]
Don't use GNOME, I wonder how much of GNOME Yelp pulls in
Glibc change exposing bugs Posted Nov 26, 2010 0:40 UTC (Fri) by sfeam (subscriber, #2841) [Link]
You could use konqueror instead
konqueror info:tar
Glibc change exposing bugs Posted Nov 26, 2010 1:33 UTC (Fri) by Spudd86 (guest, #51683) [Link]
Don't use KDE either... I use XFCE and try to keep most of the GNOME stuff not installed.
Glibc change exposing bugs Posted Nov 27, 2010 13:26 UTC (Sat) by paulj (subscriber, #341) [Link]
Well, if you want a web interface style GUI for info, but don't want to install either of the main two GUI environments, then... ;) Pinfo possibly is closest to what you want. A lynx/elinks style browser interface, for the terminal.
Glibc change exposing bugs Posted Nov 12, 2010 10:36 UTC (Fri) by marcH (subscriber, #57642) [Link]
You are mixing in the same very short post three entirely unrelated things:
- the info format - the info reader - how fine the writer sliced the document Very confusing.
|
|||||||||||||