From 8053772e54fc2f47ea92574591d7757c465a5280 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Tue, 1 May 2018 17:33:54 +0000 Subject: context-vim (18apr18) git-svn-id: svn://tug.org/texlive/trunk@47531 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/context/third/vim/VERSION | 2 +- Master/texmf-dist/doc/context/third/vim/vim.txt | 27 ++++++++++++------------- 2 files changed, 14 insertions(+), 15 deletions(-) (limited to 'Master/texmf-dist/doc/context/third') diff --git a/Master/texmf-dist/doc/context/third/vim/VERSION b/Master/texmf-dist/doc/context/third/vim/VERSION index 6c676b7a0c1..2ccc03a5fa1 100644 --- a/Master/texmf-dist/doc/context/third/vim/VERSION +++ b/Master/texmf-dist/doc/context/third/vim/VERSION @@ -1 +1 @@ -2017.07.29 +2018.04.17 diff --git a/Master/texmf-dist/doc/context/third/vim/vim.txt b/Master/texmf-dist/doc/context/third/vim/vim.txt index 8e45d0f8cb6..801d1fb34c7 100644 --- a/Master/texmf-dist/doc/context/third/vim/vim.txt +++ b/Master/texmf-dist/doc/context/third/vim/vim.txt @@ -322,36 +322,35 @@ indent the TeX code. For example: \stopruby \stopitemize -Although, the source code is easy to read, the output will not be. This is -because, unlike regular TeX, `\start` ... `\stop` -environment does not ignore white space. So, the output is the same as +By default, the leading whitespace is stripped so that the output is the same +as \startitemize \item A hello world example in C \startC - #include + #include - int main() - { - printf("Hello World") - } + int main() + { + printf("Hello World") + } \stopC \item A hello world example in ruby \startruby - puts "Hello World" + puts "Hello World" \stopruby \stopitemize -So, all the code snippets are indented by nine space. To avoid this behavior, -set + +If you want to disable this, set \definevimtyping [...] [... - strip=yes, + strip=no, ...] -The default value of `strip` is `no`. +The default value of `strip` is ψ`yes`. Adding left margin ------------------ @@ -590,7 +589,7 @@ ConTeXt has two ways of indicating binary options: The core commands freely switch between the two. In some cases, `option=yes` has a different meaning than `option=on`. To avoid confusion, I have made these synonyms. Thus, whenever the documentation says `option=yes`, you may use -`option=on`. One less thing to worry about! +`option=on`. And vice-versa. One less thing to worry about! A bit of a history ------------------ -- cgit v1.2.3