any solution for : file names with '[]' break in windows PowerShell and VSCode.

[bk111]

any solution for : file names with '[]' break in windows PowerShell and VSCode.

[absidue]

@bk111 They aren't invalid characters, you just need to quote the path or escape them properly if you want powershell to not interpret them as code. The problem isn't with yt-dlp, it's with you not telling PowerShell that it should treat them as just text and not code.

[bashonly]

I don't understand. Can you explain your issue please?

[bk111]

I don't understand. Can you explain your issue please?

'[' or ']' in PowerShell of windows cannot be used as a filename. and it will lead a failure in VScode.

PowerShell>mkdir 1[1]
PowerShell>cd 1[1]
cd : Cannot find path '1[1]' because it does not exist.
At line:1 char:1

• cd 1[1]

•   + CategoryInfo          : ObjectNotFound: (1[1]:String) [Set-Location], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
  

[pukkandan]

How is that a question about yt-dlp?

[bk111]

How is that a question about yt-dlp?

Can you guys add the [] in '--restrict-filenames' and bypass them?

[sgstair]

@bk111 In particular look for parameters like -LiteralPath in the cmdlets you're using, [] has a wildcard effect if you're not using literal paths

[pukkandan]

Can you guys add the [] in '--restrict-filenames' and bypass them?

#6444 (comment)