vis

a vi-like editor based on Plan 9's structural regular expressions

git clone https://9o.is/git/vis.git

commit a0245f4d7974cfbc510416996619eb164bfebc92
parent f43cd2787b5b4d5eade7fe7cfa76bc0f56c53362
Author: Marc André Tanner <mat@brain-dump.org>
Date:   Tue, 15 Nov 2016 00:28:18 +0100

Fix documentation regarding Lua paths in README and manual page

Wether `/usr/local/share/vis` or `/usr/share/vis` is used depends
on how the configure script was invoked. However, both are never
used at the same time.

This section should be completely reworked at some point.

Diffstat:
MREADME.md | 5+++--
Mvis.1 | 6+++---
2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md @@ -477,8 +477,9 @@ highlighting. `VIS_PATH` defaults (in this order) to - The location of the `vis` binary - `$XDG_CONFIG_HOME/vis`, where `$XDG_CONFIG_HOME` refers to `$HOME/.config` if unset -- `/usr/local/share/vis` -- `/usr/share/vis` +- `/usr/local/share/vis` or `/usr/share/vis` depending on the build configuration + +Use `:help` and search for "Lua paths" to get the actual paths being used. ### Runtime Configurable Key Bindings diff --git a/vis.1 b/vis.1 @@ -33,10 +33,10 @@ refers to .B $HOME/.config if unset .TP -.B /usr/local/share/vis -.TP -.B /usr/share/vis +\fB/usr/local/share/vis\fR or \fB/usr/share/vis\fR depending on the build configuration .RE +.TP +Check \fB:help\fR to get the actual directories used by your binary. .RE .SH HELP Type