Cause of Cannot use zoxide with oh-my-posh powershell

[aguevara]

Regarding locked Issue 5704 Cannot use zoxide with oh-my-posh powershell, I encountered the same problem in powershell, and the fix was to initialize omp before zoxide, not after. The OP mentioned that changing to a piped expression fixed the issue, but the OP also changed the order of initialization, so that zoxide was initialized after omp. That is the real fix. zoxide must be initialized after omp. This is necessary because zoxide uses the prompt to work, so if zoxide is initialized before omp, the latter wipes out the former. See this comment on issue 270 by the owner of zoxide describing the fix for the same issue in bash, and my comment there