-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Name Conflict Resolution #80
Comments
Hey. Can you provide more details on the expected behavior? I'm not sure I understand the issue. Also, what do you mean by |
He mean |
It seems I have the same problem, so I can try to explain it in a simple way.
If I start in this order
only aaa will start.
On the other hand, if I start in this order
both will start.
I have done some testing and it seems to be related to the session names. In this case I hope this clarifies the problem. |
Describe the bug
If there are two or more smug config with name prefixed from one of them, and then the prefix of the name itself is running last (as it uses
$(smug config)
To get the situation here:
smug config
will give you a list, with prefixer to come later from prefixed name.for VAR in $(smug config)
will execute everything except the last one, due to prefixing issue. On the picture it'syohane-irc
vsyohane
which is shadowed byyohane-irc
upon doingsmug start yohane
until theyohane-irc
window got stopped.However:
smug config | sort
, or at least sorting the naming order fromsmug config
output, which happens to give different output from justsmug config
. Things works normally.yohane
toyohane-irc
instead vice versa. No naming conflict like what happened above.Smug config
smug config does not matter
Expected behavior
yohane-irc
andyohane
should be executed alongside in any order of execution.Output of
cat ~/.config/smug/smug.log
output log does not matter.
Smug version
0.2.7
OS you're using
Linux
The text was updated successfully, but these errors were encountered: