You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just about tried every imaginable quoting and escaping scheme to get id3 to update a tag on a file whose name contains a pair of square brackets. The offending file name is Snowfall (Extended Mix) [feat. Laura Brehm]-102047348.mp3. I would have figured that backslashes would do the job, but they don't.
% id3 'Snowfall (Extended Mix) \[feat. Laura Brehm\]-102047348.mp3'
id3: no files matching Snowfall (Extended Mix) \[feat. Laura Brehm\]-102047348.mp3
Is this a bug, or is there an undocumented different way to escape such a filename?
On a related note, it might be worthwhile to add a "literal" flag to disable interpretation of all special characters in filespecs, so that individual files can be more easily targeted. (My use case is to invoke id3 from a script, and I'm only targeting individual files.)
The text was updated successfully, but these errors were encountered:
I've just about tried every imaginable quoting and escaping scheme to get id3 to update a tag on a file whose name contains a pair of square brackets. The offending file name is
Snowfall (Extended Mix) [feat. Laura Brehm]-102047348.mp3
. I would have figured that backslashes would do the job, but they don't.Is this a bug, or is there an undocumented different way to escape such a filename?
On a related note, it might be worthwhile to add a "literal" flag to disable interpretation of all special characters in filespecs, so that individual files can be more easily targeted. (My use case is to invoke id3 from a script, and I'm only targeting individual files.)
The text was updated successfully, but these errors were encountered: