Mercurial > vim

comparison runtime/doc/usr_41.txt @ 18912:ccd16426a1f9 v8.2.0017

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.0017: OS/2 and MS-DOS are still mentioned Commit: https://github.com/vim/vim/commit/6f345a1458df2db03fba7863492404e9dc8b817c Author: Bram Moolenaar <Bram@vim.org> Date: Tue Dec 17 21:27:18 2019 +0100 patch 8.2.0017: OS/2 and MS-DOS are still mentioned Problem: OS/2 and MS-DOS are still mentioned, even though support was removed long ago. Solution: Update documentation. (Yegappan Lakshmanan, closes #5368)
author Bram Moolenaar <Bram@vim.org>
date Tue, 17 Dec 2019 21:30:04 +0100
parents af69c9335223
children 6fd567c927c0
comparison
equal deleted inserted replaced
18911:69640323f7ca 18912:ccd16426a1f9
1 *usr_41.txt* For Vim version 8.2. Last change: 2019 Nov 21 1 *usr_41.txt* For Vim version 8.2. Last change: 2019 Dec 17
2 2
3 VIM USER MANUAL - by Bram Moolenaar 3 VIM USER MANUAL - by Bram Moolenaar
4 4
5 Write a Vim script 5 Write a Vim script
6 6
1697 1697
1698 Here is a summary of items that apply to Vim scripts. They are also mentioned 1698 Here is a summary of items that apply to Vim scripts. They are also mentioned
1699 elsewhere, but form a nice checklist. 1699 elsewhere, but form a nice checklist.
1700 1700
1701 The end-of-line character depends on the system. For Unix a single <NL> 1701 The end-of-line character depends on the system. For Unix a single <NL>
1702 character is used. For MS-DOS, Windows, OS/2 and the like, <CR><LF> is used. 1702 character is used. For MS-Windows and the like, <CR><LF> is used. This is
1703 This is important when using mappings that end in a <CR>. See |:source_crnl|. 1703 important when using mappings that end in a <CR>. See |:source_crnl|.
1704 1704
1705 1705
1706 WHITE SPACE 1706 WHITE SPACE
1707 1707
1708 Blank lines are allowed and ignored. 1708 Blank lines are allowed and ignored.
1883 1883
1884 First of all you must choose a name for your plugin. The features provided 1884 First of all you must choose a name for your plugin. The features provided
1885 by the plugin should be clear from its name. And it should be unlikely that 1885 by the plugin should be clear from its name. And it should be unlikely that
1886 someone else writes a plugin with the same name but which does something 1886 someone else writes a plugin with the same name but which does something
1887 different. And please limit the name to 8 characters, to avoid problems on 1887 different. And please limit the name to 8 characters, to avoid problems on
1888 old Windows systems. 1888 old MS-Windows systems.
1889 1889
1890 A script that corrects typing mistakes could be called "typecorr.vim". We 1890 A script that corrects typing mistakes could be called "typecorr.vim". We
1891 will use it here as an example. 1891 will use it here as an example.
1892 1892
1893 For the plugin to work for everybody, it should follow a few guidelines. This 1893 For the plugin to work for everybody, it should follow a few guidelines. This