adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 8.1.1280: remarks about functionality not in Vi clutters the help

Browse Source 
Problem:    Remarks about functionality not in Vi clutters the help.
Solution:   Move all info about what is new in Vim or already existed in Vi to
            vi_diff.txt.  Remove {not in Vi} remarks. (closes #4268) Add
            "noet" to the help files modeline.  Also include many other help
            file improvements.
This commit is contained in:
Bram Moolenaar
2019-05-05 18:13:34 +02:00
parent 9a061cb78c
commit 25c9c680ec
64 changed files with 755 additions and 751 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
runtime/doc/if_pyth.txt
View File

@ -1,4 +1,4 @@
*if_pyth.txt* For Vim version 8.1. Last change: 2018 Jan 30
*if_pyth.txt* For Vim version 8.1. Last change: 2019 May 04
VIM REFERENCE MANUAL by Paul Moore
@ -19,8 +19,6 @@ The Python Interface to Vim *python* *Python*
11. Python X |python_x|
12. Building with Python support |python-building|
{Vi does not have any of these commands}
The Python 2.x interface is available only when Vim was compiled with the
|+python| feature.
The Python 3 interface is available only when Vim was compiled with the
@ -76,7 +74,6 @@ and "EOF" do not have any indent.
None. If a string is returned, it becomes the text of
the line in the current turn. The default for [range]
is the whole file: "1,$".
{not in Vi}
Examples:
>
@ -98,7 +95,7 @@ python. For example: >
*:pyfile* *:pyf*
:[range]pyf[ile] {file}
Execute the Python script in {file}. The whole
argument is used as a single file name. {not in Vi}
argument is used as a single file name.
Both of these commands do essentially the same thing - they execute a piece of
Python code, with the "current range" |python-range| set to the given line