Asymetric, cluttered configuration: Some options only accessible via CLI or keyboard or config file

[bentolor]

Description

I stumble over the asymmetric configuration in some places.

My core goal: Just run a sudo glances and have my view running as I expected. This is inhibited by a set of issues:

• Process List → Short names is only accessible via keyboard /
• Plugin Sensors can be enabled via config file disable=False in section [sensors], but setting the proposed disable=False in the [irq] section has not effect and requires either pressing Q or passing a CLI argument`.
• The update interval cannot be configured via config file nor via keyboard

As a user I'd at least expect most all of the options to be accessible via configuration file.

Are CLI options and config file options not handled by the same configuration infrastructure?

Versions

• Glances & psutil (glances -V): Glances v3.1.4.1 with PsUtil v5.5.1
• Operating System (lsb_release -a): Ubuntu 20.04 LTS

[nicolargo]

Hi @bentolor,

Process List → Short names is only accessible via keyboard / ==> You can also start Glances with the --process-short-name CLI argument.

Plugin Sensors can be enabled via config file disable=False in section [sensors], but setting the proposed disable=False in the [irq] section has not effect and requires either pressing Q or passing a CLI argument`. ==> This is an issue... IRQ is disabled by default but should take disable=False into account... I will correct it in the scope of this issue.

The update interval cannot be configured via config file nor via keyboard ==> It's true

As a user I'd at least expect most all of the options to be accessible via configuration file. Are CLI options and config file options not handled by the same configuration infrastructure? ==> Yes it is planed (see https://github.com/nicolargo/glances/issues/1432) but it is a major code refactoring. It will be done on Glances 4.0. Contributors are welcome :)

[nicolargo]

IRQ plugins error corrected in commit 924864f9 in the DEVELOP branch.

[bentolor]

Thanks for your feedback, @nicolargo

I was not aware of #1432, but I'm glad that you already identified this topic and even already got a place on the roadmap.

I guess the nature of my question indicated, that I've rather limited Python skills, what's why I wondered about the Python-idiomatic way to handle CLI and config params. So I guess I won't be the first to step in.

Regarding your fix in commit 924864f : Doesn't this change drop the effect of --enable_irq?

[nicolargo]

Duplicated, will be follow in https://github.com/nicolargo/glances/issues/1432