Better handling for removal of `nu init`

[RuiNtD]

Code of Conduct

• I agree to follow this project's Code of Conduct

What would you like to see changed?

Since removing the oh-my-posh init nu command doesn't remove the autoload script / doesn't stop OMP's script from running, this should probably be handled. Here are some suggestions:

1. Have the OMP script delete itself after running, so it needs to be remade by oh-my-posh init nu every time. Other than the extra IO this causes, this seems like the best option to me.
2. Wrap the Nu script with something like this:

   if (which oh-my-posh | is-not-empty) {}

   Not the best option by itself, since the user may still have OMP installed despite removing the init script.
3. Mention in OMP's documentation that the script needs to be manually deleted to disable it.
4. Have a command specifically for deleting the script. oh-my-posh delete-nu?

[JanDeDobbeleer]

@RuiNtD I'd rather have the second option as that's the only fool proof way. It's OK if it's there and doesn't load, people will uninstall oh-my-posh and then still have to remove manually as option 4 won't work. Fair?

[RuiNtD]

I just realized this would be a bit different with OMP compared to Aliae. The second option makes perfect sense with OMP since it would still be obvious if OMP is being applied (having a custom prompt).

My concern with that option on Aliae was if the user removed the init line but still had Aliae installed, its script would still be applied, like setting Env variables, and the user would likely not notice.

EDIT: I also just realized I typoed in my original posts oops