From b4c604692e61a263fed3acd2c79c675761285e72 Mon Sep 17 00:00:00 2001 From: Shengjing Zhu Date: Mon, 21 Dec 2020 00:10:03 +0800 Subject: [PATCH] docs: Move autocomplete distribution section next to install section Signed-off-by: Shengjing Zhu --- README.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index d8667a062..fb5ed5626 100644 --- a/README.md +++ b/README.md @@ -248,6 +248,16 @@ the autocomplete/ctr file in your `.bashrc`, or manually like: $ source ./contrib/autocomplete/ctr ``` +#### Distribution of `ctr` autocomplete for bash and zsh + +For bash, copy the `contrib/autocomplete/ctr` script into +`/etc/bash_completion.d/` and rename it to `ctr`. The `zsh_autocomplete` +file is also available and can be used similarly for zsh users. + +Provide documentation to users to `source` this file into their shell if +you don't place the autocomplete file in a location where it is automatically +loaded for the user's shell environment. + ### CRI `cri` is a [containerd](https://containerd.io/) plugin implementation of the Kubernetes [container runtime interface (CRI)](https://github.com/kubernetes/cri-api/blob/master/pkg/apis/runtime/v1alpha2/api.proto). With it, you are able to use containerd as the container runtime for a Kubernetes cluster. @@ -282,16 +292,6 @@ A Kubernetes incubator project, [cri-tools](https://github.com/kubernetes-sigs/c * [Configuring `cri` Plugins](./docs/cri/config.md) * [Configuring containerd](https://github.com/containerd/containerd/blob/master/docs/man/containerd-config.8.md) -#### Distribution of `ctr` autocomplete for bash and zsh - -For bash, copy the `contrib/autocomplete/ctr` script into -`/etc/bash_completion.d/` and rename it to `ctr`. The `zsh_autocomplete` -file is also available and can be used similarly for zsh users. - -Provide documentation to users to `source` this file into their shell if -you don't place the autocomplete file in a location where it is automatically -loaded for the user's shell environment. - ### Communication For async communication and long running discussions please use issues and pull requests on the github repo.