Improvements for omz update

[mcandre]

If the feature request is for a plugin or theme, specify it here.

No response

If the feature solves a problem you have, specify it here.

The update subcommand has some UX quirks, around basic things like the discoverability of flags, and validation, that could be likely addressed with some quick patches.

Describe the proposed feature.

Hi,

I have a few simple suggestions for the update process.

First, please consider performing exec zsh at the end of the script after an update. Currently, omz update launches a nested shell after an update. This results in some awkward interactions with SSH terminals and larger automation scripts, because of the need to sometimes, but not always, backout of the extra shell session, when in fact there are updates.

Second, the --unattended flag is difficult to discover. I'd love to see the CLI help menu extended to document this option for the update subcommand, so that it is easier to find. Some random online discussions imply such a flag, but they mostly talk about it for installation, not updating. I was only able to test the behavior of the flag by performing a manual git reset HEAD~1 --hard in the ~/.oh-my-zsh directory.

Third, the CLI validation could be improved. omz update nosuchflag appears to silently reject bad arguments. If the user supplies invalid arguments, I'd like to see a non-zero exit code and the relevant help menu.

Describe alternatives you've considered

No response

Additional context

No response

Related Issues

No response

[carlosala]

Hi Andrew, thanks for the ideas!

1. Sounds sensible to me, but it is actually what happens at the end of successful update
2. It would be great to update the help and completion to make --unattended easier to discover and document it in the README.
3. Sounds sensible as well 👍🏻