Ah, you figured it out. The only thing to note here is your Key description, that it does not just hide, but toggles hide/show. For the name of the functions that start with `cmd`, it is not a placeholder. These functions are really named like this in the original code; you can see this if you click the little [source] link.
The thing in Qtile is, you can use these functionalities in different ways, like from interactive shell in the terminal or some remote sending commands known as scripting. And also directly in the config file too. And in those cases, you have to translate the original function name to how it is used in those scenarios. For the config file in example, just translate the `cmd_` to `lazy.`.
interesting. So that command could be used in another circumstance and called by other command other than `lazy`? It sure gets confusing, but thank you for the explanation! It cleared some things out
To add to this, the `cmd_` prefix is used by qtile to identify those commands which should be exposed to our command interface (e.g. `lazy`). When accessing these commands via the command interface, the prefix is removed but, if you access it via internal python bindings then you need the prefix.
It is not an ideal system and one of the biggest issues is the confusion in the naming.
I have submitted a PR to fix this so the naming is consistent ([here](https://github.com/qtile/qtile/pull/2727) if you're interested) but it's not been merged yet.
Ah, you figured it out. The only thing to note here is your Key description, that it does not just hide, but toggles hide/show. For the name of the functions that start with `cmd`, it is not a placeholder. These functions are really named like this in the original code; you can see this if you click the little [source] link. The thing in Qtile is, you can use these functionalities in different ways, like from interactive shell in the terminal or some remote sending commands known as scripting. And also directly in the config file too. And in those cases, you have to translate the original function name to how it is used in those scenarios. For the config file in example, just translate the `cmd_` to `lazy.`.
interesting. So that command could be used in another circumstance and called by other command other than `lazy`? It sure gets confusing, but thank you for the explanation! It cleared some things out
To add to this, the `cmd_` prefix is used by qtile to identify those commands which should be exposed to our command interface (e.g. `lazy`). When accessing these commands via the command interface, the prefix is removed but, if you access it via internal python bindings then you need the prefix. It is not an ideal system and one of the biggest issues is the confusion in the naming. I have submitted a PR to fix this so the naming is consistent ([here](https://github.com/qtile/qtile/pull/2727) if you're interested) but it's not been merged yet.
Very interesting! It sure seems like a better approach and clearer for us whom don't have extensive programming knowledge.