| #!/bin/bash | |
| for f in "$@"; do | |
| [[ "$f" != *.flac ]] && continue | |
| album="$(metaflac --show-tag=album "$f" | sed 's/[^=]*=//')" | |
| artist="$(metaflac --show-tag=artist "$f" | sed 's/[^=]*=//')" | |
| date="$(metaflac --show-tag=date "$f" | sed 's/[^=]*=//')" | |
| title="$(metaflac --show-tag=title "$f" | sed 's/[^=]*=//')" | |
| year="$(metaflac --show-tag=date "$f" | sed 's/[^=]*=//')" | |
| genre="$(metaflac --show-tag=genre "$f" | sed 's/[^=]*=//')" |
| @echo off | |
| REM Does generate.py exist, if so lets assume all of this script has been ran already and just execute the demo. | |
| if exist %~dp0generate.py goto launch | |
| REM If this script wasn't run in the context needed to install needed components lets prompt the user for their permission to do so. | |
| >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system" | |
| if '%errorlevel%' NEQ '0' ( |
When working with Python development tools like pyenv and poetry within the Windows Subsystem for Linux (WSL), users may encounter conflicts and issues due to path and environment settings. This guide aims to address these issues by outlining the steps necessary to properly configure your environment to avoid conflicts between Windows and Linux tools.
Users might experience errors similar to the following when trying to use pyenv installed on Windows from within WSL: