GitLab

https://github.com/mfaerevaag/wd/commit/3d20d15d58b9349f872a1abab639aae02374f64c

Fixes #9002

Co-authored-by: Marc Cornellà <marc.cornella@live.com>

Fixes #9050

Fixes #7609
Closes #8191
Co-authored-by: Michal Grňo <m93a.cz@gmail.com>

Fixes #8468

This solves the problem where the used pyenv is actually the one in a
Windows folder, instead of in WSL.

Fixes #9034

Fixes #8022

Closes #8342

Fixes #9136

Fixes #8925
Co-authored-by: Josh Goodall <inopinatus@inopinatus.org>

Co-authored-by: Peter J. Schroeder <peterjschroeder@gmail.com>

Closes #9122

The current check is assuming that the aws_completer is installed
globally, it then runs the command without that path

I have aws_completer in ~/.local/bin/aws_completer

This changes the check to see if the command exists instead of
concerning itself with where it in installed. This test matches the
behavior of just running the command.

Co-authored-by: Marc Cornellà <marc.cornella@live.com>

Co-authored-by: Marc Cornellà <marc.cornella@live.com>

Fixes #9114

* Suppress the problematic trap output in check_upg

The newly added trap, in systems where `rm` is aliased to `rm="rm -v"`,
shows a message stating that "update.lock" has been removed each time `zsh` is called.
I simply suppressed it with directing the output to `/dev/null`.

* Use `command` instead of >/dev/null to suppress

Co-authored-by: Babak K. Shandiz <babak.k.shandiz@gmail.com>
Co-authored-by: Marc Cornellà <marc.cornella@live.com>

Also remove unnecesary dramatic remark

Fixes #9103
Co-authored-by: Yufan You <ouuansteve@gmail.com>

* feat(mix-fast): include desctiptions (#8561)

* feat(mix-fast): improve _mix_generate (no tail, better matching)

See https://github.com/ohmyzsh/ohmyzsh/pull/9049#issuecomment-654537347

Co-authored-by: Yufan You <ouuansteve@gmail.com>

Fixes #9060 by matching a `@` in the AWS profile name.

See https://github.com/ohmyzsh/ohmyzsh/pull/8807#issuecomment-652697704

Co-authored-by: Marc Cornellà <marc.cornella@live.com>
Co-authored-by: Bartek Pacia <barpac02@gmail.com>

Co-authored-by: Marc Cornellà <marc.cornella@live.com>

`git rev-parse --is-inside-work-tree` does not have a different exit
code when not within a work tree; the difference is in the output,
either "true" when in a work tree, or "false" when not.

The if was modified similarly to the check for the hide-status config,
which also parses command output rather than exit code.
Co-authored-by: Kyle Laker <klaker@easydynamics.com>