-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent command/session #139
Comments
You haven't filled out the template, please provide the required information. For example, which version of We changed the way sessions are remembered a while back and, save for a bug (which is possible), the actual Thank you. |
Yes, sorry. I'm running
So far the only indication that |
I think I might see where the issue might be. It should only occur with I'll confirm when I get a computer back and if it is the case, it is indeed not the intended behavior. |
I think I found the issue, it will be included in the 0.9.1 hotfix. Thanks for reporting. |
This is now available in the 0.9.1 version of |
Tuigreet displays, under the
CMD:
label, either the session it's about to start or the command to launch. If you manually select a session, for example "Sway", you will getCMD: Sway
, and then you will login into sway. However, if you ask tuigreet to remember it, at the next login you will be presented withCMD: sway
, which is the command.Here session and command are almost the same, but take for example the case of SwayFX, where the session is called "SwayFX" but shares the same command
sway
.I think if tuigreet last started a session, and not a command, it should display the session name. But I also think a better solution would be to provide the name of the session and the command separately, as to avoid all confusion. Something like
Or even
Thanks for the attention.
The text was updated successfully, but these errors were encountered: