Let's document: cups

[pixelcmtd]

• cancel → cancel, lpmove: add pages and pt_BR translation #11843
• cups-config → cups-config, cupsd, lpinfo: add page #6623
• cupsaccept → cups{accept,reject,enable,disable}: add pages; lpstat: add pt_BR translation #11826
• cupsctl → cupsctl, lpq, lprm, lpadmin, lpoptions: add pages #11745
• cupsd → cups-config, cupsd, lpinfo: add page #6623
• cupsdisable → cups{accept,reject,enable,disable}: add pages; lpstat: add pt_BR translation #11826
• cupsenable → cups{accept,reject,enable,disable}: add pages; lpstat: add pt_BR translation #11826
• [ ] cupsfilter DEPRECATED
• cupsreject → cups{accept,reject,enable,disable}: add pages; lpstat: add pt_BR translation #11826
• cupstestppd → cupstestppd: add page #11898
• ippevepcl → ippeve{printer,pcl,ps}: add pages #11846
• ippeveprinter → ippeve{printer,pcl,ps}: add pages #11846
• ippeveps → ippeve{printer,pcl,ps}: add pages #11846
• ippfind → ippfind: add page #12166
• ipptool → ipptool: add page #12043
• lpadmin → cupsctl, lpq, lprm, lpadmin, lpoptions: add pages #11745
• lpinfo → cups-config, cupsd, lpinfo: add page #6623
• lpmove → cancel, lpmove: add pages and pt_BR translation #11843
• lpoptions → cupsctl, lpq, lprm, lpadmin, lpoptions: add pages #11745
• lpq → cupsctl, lpq, lprm, lpadmin, lpoptions: add pages #11745
• lprm → cupsctl, lpq, lprm, lpadmin, lpoptions: add pages #11745

This list is not complete at all. Look at the official documentation for more. The list contains all CUPS commands

[marchersimon]

We usually use page request only for single or a few unrelated pages.

[reinhart1010]

I might want to do cups-config and
cupsd

[reinhart1010]

@pixelcmtd You might want to update the list

[reinhart1010]

I might want to write for cupsctl as well, but I'm still not sure how to summarize parameters like:

--[no-]remote-admin
    Enables (disables) remote administration. 

in a way that complies with our current style guide.

[marchersimon]

If there's enough space left in the page, I'd go with this:

- Enable remote administration:

`cupsctl --remote-admin`

- Disable remote administration:

`cupsctl --no-remote-admin`

But if not you could combine it:

- Enable or disable remote administration:

`cupsctl --remote-admin|--no-remote-admin`

But I'm not actually sure if documenting both is even necessary. On of those has to be the default, right? We should we document it if it doesn't change anything?

[vitorhcl]

@kbdharun @sebastiaanspeck cupsfilter and some more commands that I haven't added to the list are deprecated. We don't need to document these commands, right?

[sebastiaanspeck]

@kbdharun @sebastiaanspeck cupsfilter and some more commands that I haven't added to the list are deprecated. We don't need to document these commands, right?

AFAIK we generally don't add deprecated commands. Or do we add and document them as deprecated?

[kbdharun]

Nice catch @sebastiaanspeck (thanks for reopening).

@vitorhcl minor suggestion in PR/commit descriptions it is suggested to use terms like "For #issue" or some other wording instead of " closes #issue", " fixes #issue" and " completes #issue" when there are remaining commands not having a page yet as GitHub detects these words automatically and closes the issue when your PR/commit is merged.

[vitorhcl]

Nice catch @sebastiaanspeck (thanks for reopening).

@vitorhcl minor suggestion in PR/commit descriptions it is suggested to use terms like "For #issue" or some other wording instead of " closes #issue", " fixes #issue" and " completes #issue" when there are remaining commands not having a page yet as GitHub detects these words automatically and closes the issue when your PR/commit is merged.

Oooh, got it, thanks for the tip.