Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUX: "DispVM" is Ambiguous #4025
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Jun 21, 2018
Member
I would expect this to say "Default DisplayVM" because "DisplayVM" is how the documentation refers to this.
No, it doesn't. There's no such thing as a "DisplayVM" in Qubes.
Also it would be nice to have a little info popup saying "What's This?" but that is really an enhancement not a UX bugfix
Duplicate of #2211.
Now it says "DispVM" and that is ambiguous.
No, it's not. The only thing "DispVM" abbreviates is "DisposableVM" (in the context of Qubes).
No, it doesn't. There's no such thing as a "DisplayVM" in Qubes.
Duplicate of #2211.
No, it's not. The only thing "DispVM" abbreviates is "DisposableVM" (in the context of Qubes). |
andrewdavidwong
closed this
Jun 21, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Duplicate of #2211 |
qubesissues commentedJun 20, 2018
Qubes OS version:
4.0
Affected component(s):
Qubes Manager
Steps to reproduce the behavior:
Go into the "Advanced Settings" tabl of any Qube's settings. Look under "Other" and see "Default DispVM"
Expected behavior:
I would expect this to say "Default DisplayVM" because "DisplayVM" is how the documentation refers to this.
Also it would be nice to have a little info popup saying "What's This?" but that is really an enhancement not a UX bugfix
Actual behavior:
Now it says "DispVM" and that is ambiguous. Myself thought this meant "DisplayVM" and I searched and searched for DisplayVM documentation and I found none. So I didn't know what this was, or why it was there. (Actually I still don't know why it is there but at least I know that it is a DisposableVM)
General notes:
Why is this in Qube Settings anyway? Is there doc on this? I can edit the docs but I need to know the answers first.
Related issues:
This is the kind of confusion that is caused by this ambiguity:
#3992
#3993