suggestion: optionally start workspace IDs from 1

[atopia]

I totally get that arrays start from 0, but the idea of a "workspace 0" never really made sense to me, because I usually map Super-1 to the first workspace, Super-2 to the second and so on. I can obviously remap those keybindings to whatever workspace ID I want, but the reported ID is also used in noctalia v5's workspace widget (noctalia doesn't accept ID 0 and changes it to 1, but that's on them). So now I'm pressing Super-3 to jump to the workspace with ID 2, which is confusing, but mapping Super-1 to mean the 2nd workspace (with ID 1) also doesn't feel right.

I realize that this would be a breaking change and people might simply disagree with my petty problem, but it would be great if the ID start could be configurable or something. Otherwise feel free to close this issue, after all it is a matter of my mental model.

[nferhat]

I can see a world where this would make sense, after all, you do think of workspaces as workspace number one, number two, etc. And in all fairness I do things like that, for example in my tmux config I do make panes 1-indexed.

I realize that this would be a breaking change and people might simply disagree with my petty problem

This can be absolutely benign, depending on how people consume the IPC data.

noctalia doesn't accept ID 0 and changes it to 1, but that's on them

They are probably using ext-workspace in order to fetch the data, but I'm not sure, also, weird quirk.