| |||||||||||||
manmanPosted Jun 15, 2009 18:32 UTC (Mon) by boudewijn (subscriber, #14185)In reply to: man by ballombe Parent article: Linux Mint 7 "Gloria"
Yes and? KDE is a gui environment and it provides manuals -- written to
the best of the abilities of the volunteer developers and writers -- available directly from the gui of the application.
That means that man pages are obsolete for KDE. man does not offer
(Log in to post comments)
man Posted Jun 16, 2009 6:01 UTC (Tue) by hppnq (guest, #14462) [Link] man does not offer anything useful that is not offered by a proper help system. man is a proper help system.
man Posted Jun 16, 2009 7:17 UTC (Tue) by k8to (subscriber, #15413) [Link]
> man is a proper help system.
Yes, yes! A thousand times yes.
man Posted Jun 16, 2009 7:28 UTC (Tue) by boudewijn (subscriber, #14185) [Link]
Yeah, full of useful features like... screenshots? hyperlinks? Give up, I'm as nostalgic and
conservative a Unix user as the next forty-year old, but man as a help system for gui applications is just plain silly. We've got something better now and man is no longer a proper help system.
man Posted Jun 16, 2009 12:26 UTC (Tue) by hppnq (guest, #14462) [Link] Eh, what is your point? Manpages are integrated in KDE on multiple levels, like they should be. In the special case of applications with a GUI, there are very good reasons why they (should) have manpages: they have a CLI interface. RTFM.
man Posted Jun 16, 2009 13:28 UTC (Tue) by nye (guest, #51576) [Link]
KDE comes with numerous commands which are entirely undocumented, including command-line-only ones. Typically these would be executed by other programs, but not always, and not always successfully. Plus when you are looking for a command without remembering exactly what it's called, and tab-completion gives you loads of options for undocumented binaries in your $PATH, it's really annoying. Having at least a description of what the program is for and what its options are would be rather more pleasant than using 'strings' on the binary.
I realise this argument is somewhat weakened by the fact that I cannot remember off-hand what commands I've had these problems with, but they are a contributing factor to KDE4 annoyance.
On a related note, are the GUI parts of KDE4 mostly documented these days? Last time I tried with the KDE4 docs they were a combination of missing, outdated, and useless (that's not just a KDE4 thing though: loads of apps in KDE3.x for years kept documentation for versions long since gone). I know for certain that there are parts of KDE4 where there are confusing options with absolutely no description of what they do (try getting some documentation on the desktop effects settings in systemsettings).
|
|||||||||||||