Open ladywhiskers opened 1 year ago
Thanks for filing this! To summarize, the problem exists somewhere in between the log-file emitter and the log-file parser. The options, to me, seem like one of these:
;
characters in paths, and the parser learns to recognize those escapes.
Problem
Running this command in verbose (
-vv
) mode:Led to this problem:
See #4937 for further detail - in summary the log file partser can't distinguish between
;
that occur inside paths and ones that separate paths.Setup
My configuration (output of
beet config
) is: