You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When user calls cupsctl, f.e. cupsctl --remote-any or cupsctl --debug-logging, almost all comments and empty lines removed. Probably ignoring empty lines could be fine, but removing comments IMHO reduces readability.
The text was updated successfully, but these errors were encountered:
By the way:
This is the reason why I personally never use cupsctl.
Strictly speaking this is even a critical bug because
user data (user comments in config files are user data)
has to be sacrosanct - always.
As far as I know cupsd.conf is still also meant for users
to manually specify their settings (when cupsd is not running).
FWIW, the reason its been implemented this way for so many years is to avoid having the comments get out of sync - for example (from the stock cupsd.conf file):
# Log general information in error_log - change "warn" to "debug"
# for troubleshooting...
LogLevel warn
Also, If you do decide to preserve comments, don't add new ones... :)
When user calls cupsctl, f.e.
cupsctl --remote-any
orcupsctl --debug-logging
, almost all comments and empty lines removed. Probably ignoring empty lines could be fine, but removing comments IMHO reduces readability.The text was updated successfully, but these errors were encountered: