2022-03-03 21:19:40 -05:00
|
|
|
<p align="center">
|
|
|
|
<a href="https://github.com/zimfw/zimfw/releases"><img src="https://img.shields.io/github/v/release/zimfw/zimfw"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/issues"><img src="https://img.shields.io/github/issues/zimfw/zimfw.svg"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/network/members"><img src="https://img.shields.io/github/forks/zimfw/zimfw.svg"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/stargazers"><img src="https://img.shields.io/github/stars/zimfw/zimfw.svg"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/releases"><img src="https://img.shields.io/github/downloads/zimfw/zimfw/total.svg"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/discussions"><img src="https://img.shields.io/badge/forum-online-green.svg"></a>
|
|
|
|
<a href="https://github.com/zimfw/zimfw/blob/master/LICENSE"><img alt="GitHub" src="https://img.shields.io/github/license/zimfw/zimfw"></a>
|
|
|
|
</p>
|
|
|
|
|
2015-12-17 07:44:19 -05:00
|
|
|
<div align="center">
|
2018-01-01 07:58:41 -05:00
|
|
|
<a href="https://github.com/zimfw/zimfw">
|
2021-01-14 09:29:16 -05:00
|
|
|
<img width="600" src="https://zimfw.github.io/images/zimfw-banner@2.jpg">
|
2015-12-17 07:44:19 -05:00
|
|
|
</a>
|
|
|
|
</div>
|
|
|
|
|
2015-12-15 00:12:17 -05:00
|
|
|
What is Zim?
|
|
|
|
------------
|
2022-03-03 21:19:40 -05:00
|
|
|
Zim is a Zsh configuration framework that bundles a [plugin manager](#usage),
|
|
|
|
useful [modules], and a wide variety of [themes], without compromising on [speed].
|
2015-12-15 00:12:17 -05:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
Check how Zim compares to other frameworks and plugin managers:
|
2015-12-15 00:12:17 -05:00
|
|
|
|
2021-08-08 21:44:37 -04:00
|
|
|
<a href="https://github.com/zimfw/zimfw/wiki/Speed">
|
|
|
|
<img src="https://zimfw.github.io/images/results.svg">
|
|
|
|
</a>
|
2015-12-18 13:34:24 -05:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
Table of Contents
|
|
|
|
-----------------
|
|
|
|
* [Installation](#installation)
|
|
|
|
* [Automatic installation](#automatic-installation)
|
|
|
|
* [Manual installation](#manual-installation)
|
|
|
|
* [Set up `~/.zshrc`](#set-up-zshrc)
|
|
|
|
* [Create `~/.zimrc`](#create-zimrc)
|
|
|
|
* [Usage](#usage)
|
|
|
|
* [`zmodule`](#zmodule)
|
|
|
|
* [`zimfw`](#zimfw)
|
|
|
|
* [Settings](#settings)
|
|
|
|
* [Uninstalling](#uninstalling)
|
2021-08-10 11:38:01 -04:00
|
|
|
|
2015-12-15 00:12:17 -05:00
|
|
|
Installation
|
|
|
|
------------
|
2022-03-03 21:19:40 -05:00
|
|
|
Installing Zim is easy. You can choose either the automatic or manual method below:
|
|
|
|
|
|
|
|
### Automatic installation
|
|
|
|
|
|
|
|
This will install a predefined set of modules and a theme for you.
|
2015-12-15 00:12:17 -05:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
* With `curl`:
|
2019-01-22 19:40:43 -05:00
|
|
|
|
2021-11-15 19:37:40 -05:00
|
|
|
curl -fsSL https://raw.githubusercontent.com/zimfw/install/master/install.zsh | zsh
|
2019-01-22 19:40:43 -05:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
* With `wget`:
|
2019-01-22 19:40:43 -05:00
|
|
|
|
2021-11-15 19:37:40 -05:00
|
|
|
wget -nv -O - https://raw.githubusercontent.com/zimfw/install/master/install.zsh | zsh
|
2015-12-15 00:12:17 -05:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
Restart your terminal and you're done. Enjoy your Zsh IMproved! Take some time
|
|
|
|
to tweak your [`~/.zshrc`](#set-up-zshrc) file, and to also check the available
|
|
|
|
[modules] and [themes] you can add to your [`~/.zimrc`](#create-zimrc).
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2019-12-04 07:22:17 -05:00
|
|
|
### Manual installation
|
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
1. Set Zsh as the default shell, if you haven't done so already:
|
|
|
|
```zsh
|
|
|
|
chsh -s $(which zsh)
|
|
|
|
````
|
|
|
|
|
|
|
|
2. [Set up your `~/.zshrc` file](#set-up-zshrc)
|
|
|
|
|
|
|
|
3. [Create your `~/.zimrc` file](#create-zimrc)
|
|
|
|
|
|
|
|
4. Restart your terminal and you're done. Enjoy your Zsh IMproved!
|
|
|
|
|
|
|
|
#### Set up `~/.zshrc`
|
|
|
|
|
|
|
|
Add the lines below to your `~/.zshrc` file, in the following order:
|
|
|
|
|
|
|
|
1. To use our `degit` tool by default to install modules:
|
|
|
|
```zsh
|
|
|
|
zstyle ':zim:zmodule' use 'degit'
|
|
|
|
````
|
|
|
|
This is optional, and only required if you don't have `git` installed (yes,
|
|
|
|
Zim works even without `git`!)
|
|
|
|
|
|
|
|
2. To set where the directory used by Zim will be located:
|
|
|
|
```zsh
|
|
|
|
ZIM_HOME=~/.zim
|
|
|
|
```
|
|
|
|
The value of `ZIM_HOME` can be any directory your user has write access to.
|
|
|
|
You can even set it to a cache directory like `${XDG_CACHE_HOME}/zim` or
|
|
|
|
`~/.cache/zim` if you also include the step below, that automatically
|
|
|
|
downloads the `zimfw` plugin manager.
|
|
|
|
|
|
|
|
3. To automatically download the `zimfw` plugin manager if missing:
|
|
|
|
```zsh
|
|
|
|
# Download zimfw plugin manager if missing.
|
|
|
|
if [[ ! -e ${ZIM_HOME}/zimfw.zsh ]]; then
|
|
|
|
curl -fsSL --create-dirs -o ${ZIM_HOME}/zimfw.zsh \
|
|
|
|
https://github.com/zimfw/zimfw/releases/latest/download/zimfw.zsh
|
|
|
|
fi
|
|
|
|
```
|
|
|
|
Or if you use `wget` instead of `curl`:
|
|
|
|
```zsh
|
|
|
|
# Download zimfw plugin manager if missing.
|
|
|
|
if [[ ! -e ${ZIM_HOME}/zimfw.zsh ]]; then
|
|
|
|
mkdir -p ${ZIM_HOME} && wget -nv -O ${ZIM_HOME}/zimfw.zsh \
|
|
|
|
https://github.com/zimfw/zimfw/releases/latest/download/zimfw.zsh
|
|
|
|
fi
|
|
|
|
```
|
|
|
|
This is optional. If you choose to not include this step, you should manually
|
|
|
|
download the `zimfw.zsh` script once and keep it at `${ZIM_HOME}`.
|
|
|
|
|
|
|
|
4. To automatically install missing modules and update the initialization script
|
|
|
|
if missing or outdated:
|
|
|
|
```zsh
|
|
|
|
# Install missing modules, and update ${ZIM_HOME}/init.zsh if missing or outdated.
|
|
|
|
if [[ ! ${ZIM_HOME}/init.zsh -nt ${ZDOTDIR:-${HOME}}/.zimrc ]]; then
|
|
|
|
source ${ZIM_HOME}/zimfw.zsh init -q
|
|
|
|
fi
|
|
|
|
```
|
|
|
|
This step is optional, but highly recommended. If you choose to not include
|
|
|
|
it, you must remember to manually run `zimfw install` every time after you
|
|
|
|
update your [`~/.zimrc`](#create-zimrc) file.
|
|
|
|
|
|
|
|
5. To source the initialization script, that initializes your modules:
|
|
|
|
```zsh
|
|
|
|
# Initialize modules.
|
|
|
|
source ${ZIM_HOME}/init.zsh
|
|
|
|
```
|
|
|
|
|
|
|
|
#### Create `~/.zimrc`
|
|
|
|
|
|
|
|
You must create your `.zimrc` file at `~/.zimrc`, if the `ZDOTDIR` environment
|
|
|
|
variable is not defined. Otherwise, it must be at `${ZDOTDIR}/.zimrc`. It's
|
|
|
|
referred to as `~/.zimrc` in the documentation for the sake of simplicity.
|
|
|
|
|
|
|
|
You can start with just:
|
|
|
|
```zsh
|
|
|
|
zmodule zsh-users/zsh-syntax-highlighting
|
|
|
|
zmodule zsh-users/zsh-autosuggestions
|
|
|
|
```
|
2022-03-18 23:43:01 -04:00
|
|
|
|
|
|
|
If you also want one of our prompt [themes]:
|
|
|
|
```
|
|
|
|
zmodule asciiship
|
|
|
|
zmodule zsh-users/zsh-syntax-highlighting
|
|
|
|
zmodule zsh-users/zsh-autosuggestions
|
|
|
|
```
|
|
|
|
|
|
|
|
If you want to use our [completion] module too, instead of using `compinit` directly:
|
2022-03-03 21:19:40 -05:00
|
|
|
```zsh
|
2022-03-18 23:43:01 -04:00
|
|
|
zmodule asciiship
|
2022-03-03 21:19:40 -05:00
|
|
|
zmodule zsh-users/zsh-completions --fpath src
|
|
|
|
zmodule completion
|
|
|
|
zmodule zsh-users/zsh-syntax-highlighting
|
|
|
|
zmodule zsh-users/zsh-autosuggestions
|
|
|
|
```
|
|
|
|
The [completion] module calls `compinit` for you. You should remove any
|
|
|
|
`compinit` calls from your `~/.zshrc` when you use this module. The modules will
|
|
|
|
be initialized in the order they are defined, and [completion] must be
|
2022-03-06 17:28:23 -05:00
|
|
|
initialized *after* all modules that add completion definitions, so it must come
|
|
|
|
after [zsh-users/zsh-completions].
|
2022-03-03 21:19:40 -05:00
|
|
|
|
2022-03-06 17:28:23 -05:00
|
|
|
Check the [`zmodule` usage](#zmodule) below for more examples on how to use it to
|
2022-03-03 21:19:40 -05:00
|
|
|
define the modules you want to use.
|
2021-07-01 18:58:49 -04:00
|
|
|
|
2019-12-01 16:00:47 -05:00
|
|
|
Usage
|
|
|
|
-----
|
2022-03-03 21:19:40 -05:00
|
|
|
The `zimfw` plugin manager builds an initialization script, at `${ZIM_HOME}/init.zsh`,
|
|
|
|
that initializes the modules you defined in your `~/.zimrc` file.
|
|
|
|
|
|
|
|
The `~/.zimrc` file must contain a `zmodule` call for each module you want to
|
|
|
|
use. The modules will be initialized in the order they are defined.
|
|
|
|
|
|
|
|
The `~/.zimrc` file is not sourced during Zsh startup, and it's only used to
|
|
|
|
configure the `zimfw` plugin manager.
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2022-03-06 17:28:23 -05:00
|
|
|
Check [examples of `~/.zimrc` files](#create-zimrc) above.
|
2021-11-06 18:04:47 -04:00
|
|
|
|
2019-12-01 16:00:47 -05:00
|
|
|
### zmodule
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2021-11-08 20:27:14 -05:00
|
|
|
Below are some usage examples:
|
|
|
|
|
2022-01-10 20:41:50 -05:00
|
|
|
* A module from the [@zimfw] organization: `zmodule archive`
|
2021-11-08 20:27:14 -05:00
|
|
|
* A module from another GitHub organization: `zmodule StackExchange/blackbox`
|
|
|
|
* A module with a custom URL: `zmodule https://gitlab.com/Spriithy/basher.git`
|
|
|
|
* A module at an absolute path, that is already installed:
|
|
|
|
`zmodule /usr/local/share/zsh-autosuggestions`
|
|
|
|
* A module with a custom fpath: `zmodule zsh-users/zsh-completions --fpath src`
|
2022-01-25 09:32:50 -05:00
|
|
|
* A module with a custom initialization file, and with git submodules disabled:
|
|
|
|
`zmodule spaceship-prompt/spaceship-prompt --source spaceship.zsh --no-submodules` or
|
|
|
|
`zmodule spaceship-prompt/spaceship-prompt --name spaceship --no-submodules`
|
2021-11-08 20:27:14 -05:00
|
|
|
* A module with two custom initialization files:
|
|
|
|
`zmodule sindresorhus/pure --source async.zsh --source pure.zsh`
|
2022-01-10 20:41:50 -05:00
|
|
|
* A module with a custom initialization command:
|
|
|
|
`zmodule skywind3000/z.lua --cmd 'eval "$(lua {}/z.lua --init zsh enhanced once)"'`
|
2022-05-07 17:31:08 -04:00
|
|
|
* A module with an on-pull command. It can be used to create a cached initialization script:
|
|
|
|
`zmodule skywind3000/z.lua --on-pull 'lua z.lua --init zsh enhanced once >! init.zsh'`
|
2021-11-08 20:27:14 -05:00
|
|
|
* A module with a big git repository: `zmodule romkatv/powerlevel10k --use degit`
|
2021-11-06 18:04:47 -04:00
|
|
|
|
|
|
|
<details id="zmodule-usage">
|
|
|
|
<summary>Want help with the complete <code>zmodule</code> usage?</summary>
|
|
|
|
|
2021-08-10 11:38:01 -04:00
|
|
|
<pre>Usage: <b>zmodule</b> <url> [<b>-n</b>|<b>--name</b> <module_name>] [options]
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2021-11-08 20:05:32 -05:00
|
|
|
Add <b>zmodule</b> calls to your <b>~/.zimrc</b> file to define the modules to be initialized. The modules
|
|
|
|
are initialized in the same order they are defined.
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2020-10-11 13:24:01 -04:00
|
|
|
<url> Module absolute path or repository URL. The following URL formats
|
2021-11-08 20:05:32 -05:00
|
|
|
are equivalent: <b>foo</b>, <b>zimfw/foo</b>, <b>https://github.com/zimfw/foo.git</b>.
|
|
|
|
<b>-n</b>|<b>--name</b> <module_name> Set a custom module name. Default: the last component in <url>.
|
|
|
|
Use slashes inside the name to organize the module into subdirec-
|
|
|
|
tories.
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2020-01-15 12:35:30 -05:00
|
|
|
Repository options:
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>-b</b>|<b>--branch</b> <branch_name> Use specified branch when installing and updating the module.
|
2021-11-08 20:05:32 -05:00
|
|
|
Overrides the tag option. Default: the repository default branch.
|
|
|
|
<b>-t</b>|<b>--tag</b> <tag_name> Use specified tag when installing and updating the module. Over-
|
|
|
|
rides the branch option.
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>-u</b>|<b>--use</b> <<b>git</b>|<b>degit</b>> Install and update the module using the defined tool. Default is
|
2021-11-08 20:05:32 -05:00
|
|
|
either defined by <b>zstyle ':zim:zmodule' use '</b><<b>git</b>|<b>degit</b>><b>'</b>, or <b>git</b>
|
|
|
|
if none is provided.
|
|
|
|
<b>git</b> requires git itself. Local changes are preserved on updates.
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>degit</b> requires curl or wget, and currently only works with GitHub
|
2021-11-08 20:05:32 -05:00
|
|
|
URLs. Modules install faster and take less disk space. Local
|
|
|
|
changes are lost on updates. Git submodules are not supported.
|
2022-01-25 09:32:50 -05:00
|
|
|
<b>--no-submodules</b> Don't install or update git submodules.
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>-z</b>|<b>--frozen</b> Don't install or update the module.
|
2022-05-07 17:31:08 -04:00
|
|
|
<b>--on-pull</b> <command> Execute command after installing or updating the module. The com-
|
|
|
|
mand is executed in the module root directory.
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2020-01-15 12:35:30 -05:00
|
|
|
Initialization options:
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>-f</b>|<b>--fpath</b> <path> Add specified path to fpath. The path is relative to the module
|
|
|
|
root directory. Default: <b>functions</b>, if the subdirectory exists.
|
|
|
|
<b>-a</b>|<b>--autoload</b> <func_name> Autoload specified function. Default: all valid names inside the
|
2021-11-15 19:37:40 -05:00
|
|
|
<b>functions</b> subdirectory, if any.
|
2021-11-08 20:05:32 -05:00
|
|
|
<b>-s</b>|<b>--source</b> <file_path> Source specified file. The file path is relative to the module
|
|
|
|
root directory. Default: <b>init.zsh</b>, if the <b>functions</b> subdirectory
|
2022-01-25 09:32:50 -05:00
|
|
|
also exists, or the largest of the files with name matching
|
2021-11-08 20:05:32 -05:00
|
|
|
<b>{init.zsh,module_name.{zsh,plugin.zsh,zsh-theme,sh}}</b>, if any.
|
|
|
|
<b>-c</b>|<b>--cmd</b> <command> Execute specified command. Occurrences of the <b>{}</b> placeholder in
|
|
|
|
the command are substituted by the module root directory path.
|
|
|
|
I.e., <b>-s 'foo.zsh'</b> and <b>-c 'source {}/foo.zsh'</b> are equivalent.
|
2021-08-10 11:38:01 -04:00
|
|
|
<b>-d</b>|<b>--disabled</b> Don't initialize or uninstall the module.
|
2021-11-06 18:04:47 -04:00
|
|
|
|
2021-11-08 20:05:32 -05:00
|
|
|
Setting any initialization option above will disable all the default values from the other
|
|
|
|
initialization options, so only your provided values are used. I.e. these values are either
|
|
|
|
all automatic, or all manual.
|
2020-05-02 19:47:38 -04:00
|
|
|
</pre>
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2021-11-06 18:04:47 -04:00
|
|
|
</details>
|
|
|
|
|
2019-12-01 16:00:47 -05:00
|
|
|
### zimfw
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2022-03-03 21:19:40 -05:00
|
|
|
The Zim plugin manager:
|
2019-12-07 21:17:40 -05:00
|
|
|
|
2021-11-08 20:27:14 -05:00
|
|
|
* Added new modules to `~/.zimrc`? Run `zimfw install`.
|
|
|
|
* Removed modules from `~/.zimrc`? Run `zimfw uninstall`.
|
|
|
|
* Want to update your modules to their latest revisions? Run `zimfw update`.
|
|
|
|
* Want to upgrade `zimfw` to its latest version? Run `zimfw upgrade`.
|
2022-03-03 21:19:40 -05:00
|
|
|
* For more information about the `zimfw` plugin manager, run `zimfw help`.
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2020-01-15 12:35:30 -05:00
|
|
|
Settings
|
|
|
|
--------
|
2021-08-10 11:38:01 -04:00
|
|
|
Modules are installed using `git` by default. If you don't have `git`
|
|
|
|
installed, or if you want to take advantage of our degit tool for faster and
|
|
|
|
lighter module installations, you can set degit as the default tool with:
|
|
|
|
|
|
|
|
zstyle ':zim:zmodule' use 'degit'
|
|
|
|
|
2020-05-26 09:02:25 -04:00
|
|
|
By default, `zimfw` will check if it has a new version available every 30 days.
|
2020-01-15 12:35:30 -05:00
|
|
|
This can be disabled with:
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
2020-01-15 12:35:30 -05:00
|
|
|
zstyle ':zim' disable-version-check yes
|
Add a plugin mechanism \o/
This is a major change, where Zsh modules/plugins are not git submodules
in the Zim repo anymore, but customized and installed separately as
individual repositories. The discussion about this started more than 2
years ago in #88. Closes #299.
This will allow contributors' modules to live in their own repositories.
See #33, #138, #262, #281, #324.
The current code has what, up to this point, I considered to be the best
balance between simplicity, execution speed and number of files.
One measured decision was to make the initialization of modules depend
only on the `':zim' modules` style, keeping it as fast as possible.
The `':zim:module' module` style is used to install, update and clean
the modules, all operations that happen after the user got his
as-blazing-fast-possible shell prompt.
Even though I didn't care much about making install or update fast,
`xargs` has a nice feature of allowing commands to be executed in
parallel with `-P`. I took advantage of that.
I've also worked on making the `zimfw` utility give the user some nice
(while still minimalistic) output. Also I'm suggesting this as the new
name for the `zmanage` tool, since `zimfw` does not shadow the `zim`
wiki tool.
2019-01-07 18:25:34 -05:00
|
|
|
|
|
|
|
Uninstalling
|
|
|
|
------------
|
|
|
|
The best way to remove Zim is to manually delete `~/.zim`, `~/.zimrc`, and
|
2019-12-14 22:41:19 -05:00
|
|
|
remove the initialization lines from your `~/.zshenv`, `~/.zshrc` and `~/.zlogin`.
|
2016-09-05 18:36:44 -04:00
|
|
|
|
2021-07-01 18:58:49 -04:00
|
|
|
[modules]: https://zimfw.sh/docs/modules/
|
|
|
|
[themes]: https://zimfw.sh/docs/themes/
|
2022-03-03 21:19:40 -05:00
|
|
|
[speed]: https://github.com/zimfw/zimfw/wiki/Speed
|
2022-01-10 20:41:50 -05:00
|
|
|
[@zimfw]: https://github.com/zimfw
|
2022-03-03 21:19:40 -05:00
|
|
|
[completion]: https://github.com/zimfw/completion
|
|
|
|
[zsh-users/zsh-completions]: https://github.com/zsh-users/zsh-completions
|