Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • elois-substrate-v0.9.23
  • elois-technical-commitee
  • elois-opti-cert
  • release/runtime-200
  • elois-fix-85
  • elois-rework-certs
  • elois-remove-renewable-period
  • poc-oneshot-accounts
  • hugo-cucumber-identity
  • elois-ci-binary-release
  • distance
  • release/runtime-100
  • ud-time-64
  • elois-duniter-storage
  • elois-compose-metrics
  • elois-smoldot
  • no-bootnodes
  • ts-types
  • runtime-201
  • runtime-200
  • runtime-105
  • runtime-104
  • runtime-103
  • runtime-102
  • runtime-101
  • v0.1.0
  • runtime-100
28 results

autocompletion.md

Blame
  • Forked from nodes / rust / Duniter v2S
    301 commits behind the upstream repository.
    autocompletion.md 866 B

    Autocompletion

    One can generate autocompletion for its favorite shell using the following option:

    cargo run --release -- completion --generator <GENERATOR>

    Where GENERATOR can be any of bash, elvish, fish, powershell and zsh.

    Bash

    First, get the completion file in a known place:

    mkdir -p ~/.local/share/duniter
    cargo run --release -- completion --generator bash > ~/.local/share/duniter/completion.bash

    You can now manually source the file when needed:

    source ~/.local/share/duniter/completion.bash

    Or you can automatically source it at bash startup by adding this to your ~/.bashrc file:

    [[ -f $HOME/.local/share/duniter/completion.bash ]] && source $HOME/.local/share/duniter/completion.bash

    You can now enjoy semantic completion of the ./target/release/duniter command using <Tab> key.