-
Notifications
You must be signed in to change notification settings - Fork 0
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
Plugin Names with comma in their name are impossible to specify #6
Comments
Hello! I've checked and confirm the bug. It's partial though, because "alternative" ways to provide such names exist. That's why I've never encountered it, despite using plugins with commas in names :-\
Yes, I should fix the first case. Escape sequence looks great. |
Found another funny workaround for now. Use glob or regex pattern :-D Next example simply replaces comma with a dot(which represenets any symbol in regex).
|
I personally am entirely satisfied by specifying the files as individual arguments (workaround 2), it even simplifies my script, since I don't need to concat the file names anymore and don't need multiple merge lists. I could have figured this out myself, but it seems I completely missed it in my multiple times of going over the help-output of the As to multiple merge-lists I feel like the regex workaround is a bit awkward, though I can't think of a situation where it would not work. Is there any reason we can't have multiple I'll leave it to you if you want to close the issue or keep it open. |
|
Fixes: Allow specifying plugin names with comma in their name by escaping(prepending with backspace) in --merge option thanks to Lucius Martius' report(resolve [Issue-6](#6)).
Maybe I'm overlooking something, but there seems to be no way to specify plugin names like "Umbra, Blademaster.esp" to an '-m' merge command without habasi failing because it thinks I just specified two non-existant plugins.
I can just rename the plugin and its fine, but these days plugin names carry a certain relevancy since they are used to sort load order with plox/mlox.
My suggestion would be to support an escape sequence
\,
.The text was updated successfully, but these errors were encountered: