Summary: | Manpage for balooctl | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Unknown <null> |
Component: | balooctl | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | aspotashev, info, nate, pinak.ahuja |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Unknown
2015-08-23 14:09:00 UTC
Man pages are usually for command-line tool. What Baloo command line tool do you need a manpage for? Probably balooctl: $ man balooctl No manual entry for balooctl That said, it does have a -v flag: $ balooctl -v baloo 5.39.0 *** Bug 364078 has been marked as a duplicate of this bug. *** Just running `balooctl` shows the options and what they will do. It's not a full manpage, but it's good enough IMO. The decission if this is a bug or not should not depend on YOUR opinion but on rules and regularities; e.g. goals of KDE to make the Linux Desktop usable for everyone (also granny). KDE is not a Hacker/Nerd graphical desktop environment on top of GNU Linux! A manpage should be the minimum for each application. btw: Just running `balooctl` is buggy, too because there is no version information given. Using explicite `-v` for is is unusal, too and an unneeded obstacle to the user. btw: I am not a usual KDE user. I am just a member of the FOSS community and try to improve a "product" having the FOSS movement and the users in my mind. I am not the user here. (In reply to moonkid from comment #5) > The decission if this is a bug or not should not depend on YOUR opinion but > on rules and regularities; e.g. goals of KDE to make the Linux Desktop > usable for everyone (also granny). Well, I'm one of the Baloo developers, so in fact it does depend on my opinion. :) However even if that was not true, KDE does not have a global policy that all command line tools much have manpages. Also, most grannies I know don't read manpages. They use GUI software. Can you articulate what exactly is the problem is with running `balooctl --help`? > Can you articulate what exactly is the problem is
> with running `balooctl --help`?
It is not usual in unixoid environments.
I disagree. It's extremely common and I've encountered it over and over again throughout my career using UNIX-like operating systems. And KDE's command-line programs universally use this style instead of manpages. --help and --version are indeed not a Unix standard, but a GNU standard. Many KDE tools follow GNU conventions, despite not being GNU projects. We actually try to support both standards for these two important options: -h and -v also work on most KDE programs. https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html (In reply to Nate Graham from comment #4) > Just running `balooctl` shows the options and what they will do. It's not a > full manpage, but it's good enough IMO. This only works if you have `balooctl` installed. If we had a real manpage, you could also find it online, e.g. http://manpages.org/meinproc5/8 for meinproc5. |