mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1011] Command line arguments aren't logged when using the --opt=value form #483
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#483
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @michaelherger on GitHub (Jun 5, 2022).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1011
I noticed some of my arguments were not logged when using
--verbose. Trying to figure out what was causing this I realized that--opt=valuewould not be logged, while--opt valuewas. Yet the first form seems to be accepted just fine to pass an argument to the application.@michaelherger commented on GitHub (Jun 5, 2022):
With the equal sign the
passwordargument would not be listed (please ignore the-aparam which is my own):Without the equal sign the
passwordargument is listed:I guess that while iterating arguments in
main.rswe'd need to split thekeyvalue by the=sign in case it didn't match any of the defined options. And then try again with the first part of the resulting tuple?@JasonLG1979 commented on GitHub (Jun 25, 2022):
Sorry I missed this issue. I believe I have a fix. The only side effect is that it also strips the
-and--from the log lines. So it would look like this:@michaelherger commented on GitHub (Jun 27, 2022):
Thanks, guys!