zsh-notify
zsh-notify plugin for zsh with auto install and sound of r2d2.
Features
- auto install dependencies
- sound of r2d2 for success and error commands
Requirements
This is a list of plugins that need to be installed previously to enjoy all the goodies of this configuration:
Installation
oh-my-zsh users
If you're using oh-my-zsh, install this plugin by doing the following:
- Go to your oh-my-zsh custom plugins directory -
cd ~/.oh-my-zsh/custom/plugins
- Clone the plugin
bash git clone https://github.com/luismayta/zsh-notify
bash - Edit your
.zshrc
and addplugins=( ... zsh-notify )
to your list of plugins - Open a new terminal and enjoy!
antigen users
If you're using Antigen, install this plugin by doing the following:
- Add
antigen bundle luismayta/zsh-notify
to your.zshrc
where you're adding your other plugins. - Either open a new terminal to force zsh to load the new plugin, or run
antigen bundle luismayta/zsh-notify
in a running zsh session. - Enjoy!
antibody users
If you're using Antibody, install this plugin by doing the following:
- Add :
{.sourceCode .bash}
antibody bundle luismayta/zsh-notify branch:develop
to your .zshrc
where you're adding your other plugins.
- Either open a new terminal to force zsh to load the new plugin, or run
antibody bundle luismayta/zsh-notify
in a running zsh session. - Enjoy!
Usage
The only thing that is needed is to add it to your ZSH configuration
Functions
Help
Got a question?
File a GitHub issue.
Contributing
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or file feature requests.
Development
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull Request so that we can review your changes
NOTE: Be sure to rebase the latest changes from "upstream" before making a pull request!
Module Versioning
This Module follows the principles of Semantic Versioning (SemVer).
Using the given version number of MAJOR.MINOR.PATCH
, we apply the following constructs:
- Use the
MAJOR
version for incompatible changes. - Use the
MINOR
version when adding functionality in a backwards compatible manner. - Use the
PATCH
version when introducing backwards compatible bug fixes.
Backwards compatibility in 0.0.z
and 0.y.z
version
- In the context of initial development, backwards compatibility in versions
0.0.z
is not guaranteed whenz
is increased. (Initial development) - In the context of pre-release, backwards compatibility in versions
0.y.z
is not guaranteed wheny
is increased. (Pre-release)
Copyright
Copyright © 2018-2021 Hadenlabs
Trademarks
All other trademarks referenced herein are the property of their respective owners.
License
The code and styles are licensed under the LGPL-3.0 license See project license..