Zimfw Versions Save

Fixed

• Compiled files must also be cleaned from modules defined with absolute paths.

Fixed

• "gzip: stdin: unexpected end of file" error when trying to upgrade. (See #407)

Added

• -c|-cmd option to zmodule. This allows for executing any specified command.

Fixed

• Allow local modules to be initialized and compiled in their respective directories, when absolute paths are given, instead of forcing them to be installed inside ZIM_HOME.

Fixed

• "No such file or directory" error when building a new file. This was a regression introduced after replacing cmp by cksum in version 1.2.0.
• Show warning message when nothing found to be initialized in a module.

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.

Fixed

• "no such file or directory" error before initial check for latest version.
• Show error when no modules defined in .zimrc, instead of allowing xargs to execute the action with no positional parameters.

Added

• help and version actions.
• -v verbose option. Normal mode output is now focused on the specified action.
• Asynchronously check the latest version every 30 days. This can be disabled with zstyle ':zim' disable-version-check yes.

Changed

• When upgrading, download latest release asset instead of raw file from the master branch.
• curl is preferred over wget. (See #360)
• wget's output is only shown in verbose mode.

Fixed

• Zsh 5.2 does not recognize the :P modifier. Replace it by :A.
• Also compile and clean .zprofile among the startup files.
• Don't fail on zimfw clean-dumpfile when there's nothing to remove.

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 a 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)

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.