psi-jack
/
zimfw
mirror of
1
0
Fork 0
Code Issues Releases Wiki Activity
zimfw/CHANGELOG.md

168 lines
6.4 KiB
Markdown
Raw Normal View History

Add CHANGELOG.md Closes #356. Closes #352.
2020-01-07 09:03:13 -05:00
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
Fix getting HEAD remote branch in update.zsh.erb instead of getting just the current local branch.
2021-02-17 17:51:22 -05:00
### Fixed
- Correctly get the repository's default branch. The related change in version
1.4.0 actually broke updating the modules, as new changes stopped being
fetched.
v1.4.0
2021-01-07 13:41:35 -05:00
## [1.4.0] - 2021-01-07
Fail when no parameter is provided to `-c|--cmd` Forgot to add this check when the new option was introduced.
2020-11-07 14:39:30 -05:00
### Added
Prompt before zimfw uninstall, unless `-q` is set Prompt before uninstalling modules, so users have a chance to review the list before moving forward with the action.
2020-10-26 20:32:25 -04:00
- Prompt before uninstalling modules, unless `-q` is set.
Add build date in info Fixes #421
2021-01-02 18:40:58 -05:00
- Show build date in info.
v1.3.2
2020-08-01 10:39:07 -04:00
Fail when no parameter is provided to `-c|--cmd` Forgot to add this check when the new option was introduced.
2020-11-07 14:39:30 -05:00
### Fixed
v1.4.0
2021-01-07 13:41:35 -05:00
- Show error when no parameter is provided to `-c|--cmd` in `zmodule`.
- Use repository's default branch instead of hardcoding the default to `master`,
when no branch is specified in `zmodule`.
Fail when no parameter is provided to `-c|--cmd` Forgot to add this check when the new option was introduced.
2020-11-07 14:39:30 -05:00
v1.3.2
2020-08-01 10:39:07 -04:00
## [1.3.2] - 2020-08-01
Clean compiled files from absolute path modules We were already compiling at these paths, but not cleaning the compiled files. Fixes #399
2020-07-31 22:03:47 -04:00
### Fixed
- Compiled files must also be cleaned from modules defined with absolute paths.
v1.3.1
2020-07-24 11:30:19 -04:00
## [1.3.1] - 2020-07-24
Don't pipe to gunzip gunzip should not try to seek the stream, but an issue was reported in #407, where it fails with gzip: stdin: unexpected end of file So we're writing to a file first just to be safer. Fixes #407.
2020-07-23 22:49:39 -04:00
### Fixed
Clean compiled files from absolute path modules We were already compiling at these paths, but not cleaning the compiled files. Fixes #399
2020-07-31 22:03:47 -04:00
- "gzip: stdin: unexpected end of file" error when trying to upgrade.
Don't pipe to gunzip gunzip should not try to seek the stream, but an issue was reported in #407, where it fails with gzip: stdin: unexpected end of file So we're writing to a file first just to be safer. Fixes #407.
2020-07-23 22:49:39 -04:00
(See [#407](https://github.com/zimfw/zimfw/issues/407))
v1.3.0
2020-07-05 10:36:21 -04:00
## [1.3.0] - 2020-07-05
Add `-c|--cmd` option to `zmodule` so freely defined commands can be executed. Fixes #405
2020-07-02 18:16:44 -04:00
### Added
Clean compiled files from absolute path modules We were already compiling at these paths, but not cleaning the compiled files. Fixes #399
2020-07-31 22:03:47 -04:00
- `-c|-cmd` option to `zmodule`. This allows for executing any specified command.
v1.2.2
2020-06-09 22:39:39 -04:00
## [1.2.2] - 2020-06-10
Init and compile local modules in their directories instead of requiring that they're installed inside ZIM_HOME. Fixes #399
2020-06-05 23:09:23 -04:00
### Fixed
- Allow local modules to be initialized and compiled in their respective
Clean compiled files from absolute path modules We were already compiling at these paths, but not cleaning the compiled files. Fixes #399
2020-07-31 22:03:47 -04:00
directories, when absolute paths are given, instead of forcing them to be
installed inside `ZIM_HOME`.
v1.2.1
2020-05-26 09:02:25 -04:00
## [1.2.1] - 2020-05-26
Make cksum silent so it behaves similar to `cmp -s`, which is what we had before.
2020-05-25 14:40:34 -04:00
### Fixed
v1.2.1
2020-05-26 09:02:25 -04:00
- "No such file or directory" error when building a new file. This was a
v1.2.2
2020-06-09 22:39:39 -04:00
regression introduced after replacing `cmp` by `cksum` in version 1.2.0.
Warning when no initialization found in a module Some plugins don't follow the `module_name.plugin.zsh` name, as "it is the wild west out there". Fixes #395
2020-05-25 15:01:00 -04:00
- Show warning message when nothing found to be initialized in a module.
v1.2.0
2020-05-17 11:30:14 -04:00
## [1.2.0] - 2020-05-17
Don't depend on `cmp` and `xargs` as they requires busybox or diffutils and findutils. Use `cksum` and `zargs` instead. Fixes #393
2020-05-16 21:22:22 -04:00
### Changed
- Use `cksum` instead of `cmp`, and `zargs` instead of `xargs`, so we don't
depend on busybox or diffutils and findutils.
### Fixed
- Error messages and the `zmodule` usage text.
v1.1.1
2020-01-26 15:42:03 -05:00
## [1.1.1] - 2020-01-26
Fix "no such file or directory" error before initial check for latest version. Not all versions of Zsh or all OSs are affected. Error seen with Zsh 5.6.2 running on FreeBSD is: _zimfw_version_check:10: no such file or directory: /path/to/.latest_version
2020-01-22 12:48:19 -05:00
### Fixed
- "no such file or directory" error before initial check for latest version.
Fail when no modules defined in .zimrc instead of allowing xargs to execute the action with no positional parameters. Also don't try to write to .latest_version if there's no write permission. This is supposed to be a background/optional operation, so we don't want to show an error message in this case. And use Zsh globs instead of find with -exec, and find won't fail if there's an error with the -exec command.
2020-01-26 15:33:17 -05:00
- Show error when no modules defined in .zimrc, instead of allowing xargs to
execute the action with no positional parameters.
v1.1.0 Last-minute minor fixes: * Delete .latest_version after upgrading. Having a cache brings in these complexities. * Print warning to stderr, to distinguish it from the normal output. * Update help to be in sync with the README.md.
2020-01-20 07:03:20 -05:00
## [1.1.0] - 2020-01-20
Update CHANGELOG.md
2020-01-11 16:43:13 -05:00
### Added
Add help and version actions
2020-01-13 12:24:43 -05:00
- `help` and `version` actions.
v1.1.0 Last-minute minor fixes: * Delete .latest_version after upgrading. Having a cache brings in these complexities. * Print warning to stderr, to distinguish it from the normal output. * Update help to be in sync with the README.md.
2020-01-20 07:03:20 -05:00
- `-v` verbose option. Normal mode output is now focused on the specified action.
Optional async check for latest version every 30 days, storing it in a .latest_version file. Also allow disabling this with: zstyle ':zim' disable-version-check yes
2020-01-15 12:35:30 -05:00
- Asynchronously check the latest version every 30 days. This can be disabled
with `zstyle ':zim' disable-version-check yes`.
Update CHANGELOG.md
2020-01-11 16:43:13 -05:00
### Changed
Download latest release instead of from master Using GitHub URL to latest release asset as described in https://help.github.com/en/github/administering-a-repository/linking-to-releases#linking-to-the-latest-release There's a counter of release assets downloads, which is nice. Download zimfw.zsh when installing, and zimfw.zsh.gz when upgrading, so we can have separate counts.
2020-01-11 17:17:09 -05:00
- When upgrading, download latest release asset instead of raw file from the
master branch.
Update CHANGELOG.md
2020-01-11 16:43:13 -05:00
- `curl` is preferred over `wget`.
v1.1.0 Last-minute minor fixes: * Delete .latest_version after upgrading. Having a cache brings in these complexities. * Print warning to stderr, to distinguish it from the normal output. * Update help to be in sync with the README.md.
2020-01-20 07:03:20 -05:00
(See [#360](https://github.com/zimfw/zimfw/issues/360))
Update CHANGELOG.md
2020-01-11 16:43:13 -05:00
- `wget`'s output is only shown in verbose mode.
v1.0.1
2020-01-09 07:29:40 -05:00
## [1.0.1] - 2020-01-09
Zsh 5.2 does not recognize the :P modifier It fails with _zimfw_build_init:8: unrecognized modifier `P' The `:P` modifier was introduced in Zsh 5.3. Replace it by `:A`, as we still want to keep compatibility with Zsh 5.2. Fixes #349
2020-01-08 16:45:54 -05:00
### Fixed
- Zsh 5.2 does not recognize the `:P` modifier. Replace it by `:A`.
Add .zprofile to the list of startup files Zim does not use/modify .zprofile in it's templates. For completeness/ performance, the .zprofile should be compiled/cleaned if present. Ref: http://zsh.sourceforge.net/Intro/intro_3.html Closes #358
2020-01-08 08:19:52 -05:00
- Also compile and clean .zprofile among the startup files.
Add help and version actions
2020-01-13 12:24:43 -05:00
- Don't fail on `clean-dumpfile` when there's nothing to remove.
Add CHANGELOG.md Closes #356. Closes #352.
2020-01-07 09:03:13 -05:00
## [1.0.0] - 2020-01-07
This is a major change, where modules are not git submodules in the Zim repo
anymore, but customized and installed separately as individual repositories.
External modules can more easily be installed, updated and uninstalled. This
makes Zim the first project for Zsh that is both a set of community-maintained
modules with a default installation (like on-my-zsh and prezto) and a plugin
manager (like antigen and zplug).
This version is not backwards-compatible with previous versions, so a new
installation of Zim is required.
Take your time to review the updated [README.md] and the changes listed below.
### Added
- `zimfw` CLI tool.
- `zmodule` function to define modules.
- Automatic installation script.
- zsh-users/zsh-autosuggestions is enabled by default in new installations.
### Changed
- The Zim "core" is reduced to a single file, namely zimfw.zsh, that is
self-updated without requiring git. With this, `ZIM_HOME` is not (the root of)
a git repo anymore.
- Zsh and modules are configured in .zshrc instead of .zimrc.
- .zimrc is not sourced during Zsh startup anymore, and only contains the module
definitions.
- Zim's init.zsh and login_init.zsh scripts are generated by the `zimfw` CLI
tool and contain static code. This allows for constant startup time,
regardless of how complex the module definitions are.
- Zim modules moved to individual repositories in the https://github.com/zimfw
organization.
- Zim modules are configured with `zstyle` instead of environment variables.
- Zim themes are sourced directly, instead of working with prompinit, and are
configured with environment variables instead of with promptinit parameters.
- The [environment] module is reduced in scope to to only set Zsh options. The
additional code moved to the [input] module (smart-URL widgets), the [utility]
module (default pager), and a new [termtitle] module (terminal window title).
- The minimal theme is renamed to [s1ck94].
### Removed
- `zmanage` CLI tool.
- The directory and history modules. Their code moved into the [environment]
module.
- The prompt module, and the external lean, liquidprompt and pure themes.
Use `zmodule miekg/lean`, or `zmodule nojhan/liquidprompt`, or `zmodule
sindresorhus/pure --source async.zsh --source pure.zsh` to define one of these
external themes, respectively. The Zim themes moved to individual repositories.
- Support for themes that require promptinit.
(See [#325](https://github.com/zimfw/zimfw/issues/325))
### Fixed
- `ZIM_HOME` is set in .zshenv instead of .zshrc. The issue was that the
variable was not available in .zlogin in non-interactive login shells.
[README.md]: https://github.com/zimfw/zimfw/blob/master/README.md
[environment]: https://github.com/zimfw/environment
[input]: https://github.com/zimfw/input
[utility]: https://github.com/zimfw/utility
[termtitle]: https://github.com/zimfw/termtitle
[s1ck94]: https://github.com/zimfw/s1ck94
v1.4.0
2021-01-07 13:41:35 -05:00
[Unreleased]: https://github.com/zimfw/zimfw/compare/v1.4.0...HEAD
[1.4.0]: https://github.com/zimfw/zimfw/compare/v1.3.2...v1.4.0
v1.3.2
2020-08-01 10:39:07 -04:00
[1.3.2]: https://github.com/zimfw/zimfw/compare/v1.3.1...v1.3.2
v1.3.1
2020-07-24 11:30:19 -04:00
[1.3.1]: https://github.com/zimfw/zimfw/compare/v1.3.0...v1.3.1
v1.3.0
2020-07-05 10:36:21 -04:00
[1.3.0]: https://github.com/zimfw/zimfw/compare/v1.2.2...v1.3.0
v1.2.2
2020-06-09 22:39:39 -04:00
[1.2.2]: https://github.com/zimfw/zimfw/compare/v1.2.1...v1.2.2
v1.2.1
2020-05-26 09:02:25 -04:00
[1.2.1]: https://github.com/zimfw/zimfw/compare/v1.2.0...v1.2.1
v1.2.0
2020-05-17 11:30:14 -04:00
[1.2.0]: https://github.com/zimfw/zimfw/compare/v1.1.1...v1.2.0
v1.1.1
2020-01-26 15:42:03 -05:00
[1.1.1]: https://github.com/zimfw/zimfw/compare/v1.1.0...v1.1.1
v1.1.0 Last-minute minor fixes: * Delete .latest_version after upgrading. Having a cache brings in these complexities. * Print warning to stderr, to distinguish it from the normal output. * Update help to be in sync with the README.md.
2020-01-20 07:03:20 -05:00
[1.1.0]: https://github.com/zimfw/zimfw/compare/v1.0.1...v1.1.0
v1.0.1
2020-01-09 07:29:40 -05:00
[1.0.1]: https://github.com/zimfw/zimfw/compare/v1.0.0...v1.0.1
Add CHANGELOG.md Closes #356. Closes #352.
2020-01-07 09:03:13 -05:00
[1.0.0]: https://github.com/zimfw/zimfw/compare/5d66578...v1.0.0