GitLab

Added AWS_EB_PROFILE environment variable to the AWS Plugin. The EB CLI uses this
variable instead of the primary AWS_PROFILE variable to keep track of what profile
it is using.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html

* Update the AWS plugin to support disabling RPROMT display:
  Use a $SHOW_AWS_PROMPT option.

* Refactoring aws plugin:
  Exposing customizable aws_prompt_info function to be used in themes.

* Set aws prompt prefix and suffix to original values and fix README
Co-authored-by: "Vassilis S. Moustakas" <vsmoustakas@gmail.com>

* Clean up Homebrew detection and add comments. Also changed some if flags.
* Detect aws cli completion file from RPM

Adds "givero" as a keyword for searching Givero, a relative new search engine donating revenue to good causes around the world.

Changed from `stack` because it conflicts with Haskell Tool Stack

Fixes #7659

Closes #5564

* allow kubectl commands against all namespaces

* enhance the readme too

Extra t in `wp theme updatet`

Reverts robbyrussell/oh-my-zsh#5714

Just found this typo while browsing through the `plugins` folder ... and it "hurt sme" :hurtrealbad:

Currently it shows for example the following:

  DEVICE_ID  -- transport_id:2

which doesn't really ease device selection. I've adapted the awk script to print
device name with it's model name, see the example below:

  DEVICE_ID  -- Pixel_3(blueline)

* Maven profiles for current pom.xml file
* Maven profiles for pom hierarchy
* Ommiting comments in profiles

Avoids forking to tput and some systems don't have tput

* The check for the asdf installation directory is more precise:

    The existence of the directory `$HOME/.asdf` does not mean that it is the installation
    directory of `asdf`. It will also be created after installing at least one asdf plugin.

* Completions, while installed with homebrew, are now expected on an alternative location.

This change references `$RANDOM` outside the subshell to refresh it for the
next subshell invocation. Otherwise, subsequent runs of the function get the
same value and, if run simultaneously, they may clobber each others' temp .z
files.

This is due to how zsh distributes RANDOM values when running inside a
subshell:

  subshells that reference RANDOM will result in identical pseudo-random
  values unless the value of RANDOM is referenced or seeded in the parent
  shell in between subshell invocations

See: http://zsh.sourceforge.net/Doc/Release/Parameters.html#index-RANDOM