Fisherman v0.2.0
* Improved README, added links to screencasts, updated
documentation with new changes and fixed other typos and
composition errors.
* Removed `fisher update --cache` in favor of
`fisher --cache | fisher update` and
`fisher uninstall --all` in favor of
`fisher --cache | fisher uninstall`.
* Fisherman does not move initialization / configuration
files following the convention `name`.config.fish to
`$fisher_config/functions`, but to `$fisher_config/conf.d`
now and evaluates each `*.config.fish` inside at shell
start as usual. Closes #13.
* Added `fisher --cache[=base]` option to retrieve contents
in `$fisher_cache`, eliminating flaky usage of `find(1)`.
Closes #11.
* Fisherman now generates information about plugins installed
via custom URLs. For the description, a shortened version of
the URL is used. For the URL the full URL is used. For tags,
the URL is fuzzily checked and tags such as _theme_, _plugin_,
_config_ and _omf_ are added. The tag _orphan_ is added by
default as well. Finally, the author is generated by
retrieving the e-mail or username of the author of the
first commit in the plugin's repository. Closes #9 and #14.
* Changed `--path-in-cache` to `--translate.` This function
translates an name or supported URL/URL variation into a path
inside `$fisher_cache`. This allows you to treat plugins
installed via custom URLs almost like regular plugins if they
are installed. Closes #8.
* Fixed a bug with `mktemp` failing on some systems.
Closes #7. Thanks @tobywf.
* Added [CODE_OF_CONDUCT][code_of_conduct]. Closes #6.
* Fisherman can now unload themes within the same shell,
without having to restart the session. Closes #5.
* Fisherman can now load themes within the same shell,
without having to restart the session using `exec fish`.
Shoddy themes, for example those failing to declare global
variables with the `-g` flag still require the session to
be reset. See [**related**][bobthefish-19]. Closes #4.
* Move `getopts` implementation to `share/getopts.awk`.
Closes #3.
* Support dots inside URIs in `fisher --validate`.
Closes #2.
2016-01-03 03:35:56 +00:00
|
|
|
# Contributor Code of Conduct
|
|
|
|
|
|
|
|
|
|
As contributors and maintainers of this project, and in the interest of
|
|
|
|
|
fostering an open and welcoming community, we pledge to respect all people who
|
|
|
|
|
contribute through reporting issues, posting feature requests, updating
|
|
|
|
|
documentation, submitting pull requests or patches, and other activities.
|
|
|
|
|
|
|
|
|
|
We are committed to making participation in this project a harassment-free
|
|
|
|
|
experience for everyone, regardless of level of experience, gender, gender
|
|
|
|
|
identity and expression, sexual orientation, disability, personal appearance,
|
|
|
|
|
body size, race, ethnicity, age, religion, or nationality.
|
|
|
|
|
|
|
|
|
|
Examples of unacceptable behavior by participants include:
|
|
|
|
|
|
|
|
|
|
* The use of sexualized language or imagery
|
|
|
|
|
* Personal attacks
|
|
|
|
|
* Trolling or insulting/derogatory comments
|
|
|
|
|
* Public or private harassment
|
|
|
|
|
* Publishing other's private information, such as physical or electronic
|
|
|
|
|
addresses, without explicit permission
|
|
|
|
|
* Other unethical or unprofessional conduct
|
|
|
|
|
|
|
|
|
|
Project maintainers have the right and responsibility to remove, edit, or
|
|
|
|
|
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
|
|
|
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
|
|
|
permanently any contributor for other behaviors that they deem inappropriate,
|
|
|
|
|
threatening, offensive, or harmful.
|
|
|
|
|
|
|
|
|
|
By adopting this Code of Conduct, project maintainers commit themselves to
|
|
|
|
|
fairly and consistently applying these principles to every aspect of managing
|
|
|
|
|
this project. Project maintainers who do not follow or enforce the Code of
|
|
|
|
|
Conduct may be permanently removed from the project team.
|
|
|
|
|
|
|
|
|
|
This Code of Conduct applies both within project spaces and in public spaces
|
|
|
|
|
when an individual is representing the project or its community.
|
|
|
|
|
|
|
|
|
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
2016-01-10 07:01:07 +00:00
|
|
|
reported by contacting a project maintainer at [hi@fisherman.sh](mailto:hi@fisherman.sh). All
|
Fisherman v0.2.0
* Improved README, added links to screencasts, updated
documentation with new changes and fixed other typos and
composition errors.
* Removed `fisher update --cache` in favor of
`fisher --cache | fisher update` and
`fisher uninstall --all` in favor of
`fisher --cache | fisher uninstall`.
* Fisherman does not move initialization / configuration
files following the convention `name`.config.fish to
`$fisher_config/functions`, but to `$fisher_config/conf.d`
now and evaluates each `*.config.fish` inside at shell
start as usual. Closes #13.
* Added `fisher --cache[=base]` option to retrieve contents
in `$fisher_cache`, eliminating flaky usage of `find(1)`.
Closes #11.
* Fisherman now generates information about plugins installed
via custom URLs. For the description, a shortened version of
the URL is used. For the URL the full URL is used. For tags,
the URL is fuzzily checked and tags such as _theme_, _plugin_,
_config_ and _omf_ are added. The tag _orphan_ is added by
default as well. Finally, the author is generated by
retrieving the e-mail or username of the author of the
first commit in the plugin's repository. Closes #9 and #14.
* Changed `--path-in-cache` to `--translate.` This function
translates an name or supported URL/URL variation into a path
inside `$fisher_cache`. This allows you to treat plugins
installed via custom URLs almost like regular plugins if they
are installed. Closes #8.
* Fixed a bug with `mktemp` failing on some systems.
Closes #7. Thanks @tobywf.
* Added [CODE_OF_CONDUCT][code_of_conduct]. Closes #6.
* Fisherman can now unload themes within the same shell,
without having to restart the session. Closes #5.
* Fisherman can now load themes within the same shell,
without having to restart the session using `exec fish`.
Shoddy themes, for example those failing to declare global
variables with the `-g` flag still require the session to
be reset. See [**related**][bobthefish-19]. Closes #4.
* Move `getopts` implementation to `share/getopts.awk`.
Closes #3.
* Support dots inside URIs in `fisher --validate`.
Closes #2.
2016-01-03 03:35:56 +00:00
|
|
|
complaints will be reviewed and investigated and will result in a response that
|
|
|
|
|
is deemed necessary and appropriate to the circumstances. Maintainers are
|
|
|
|
|
obligated to maintain confidentiality with regard to the reporter of an
|
|
|
|
|
incident.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
|
|
|
version 1.3.0, available at
|
|
|
|
|
[http://contributor-covenant.org/version/1/3/0/][version]
|
|
|
|
|
|
|
|
|
|
:anchor:
|
|
|
|
|
|
|
|
|
|
<!-- Links -->
|
|
|
|
|
|
|
|
|
|
[version]: http://contributor-covenant.org/version/1/3/0/
|
|
|
|
|
[homepage]: http://contributor-covenant.org
|