Mercurial > vim

comparison runtime/doc/intro.txt @ 15334:9d3d7b0f4861

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files commit https://github.com/vim/vim/commit/4c05fa08c9739e307ddc88ac91ba6d208f1fd68e Author: Bram Moolenaar <Bram@vim.org> Date: Tue Jan 1 15:32:17 2019 +0100 Update runtime files
author Bram Moolenaar <Bram@vim.org>
date Tue, 01 Jan 2019 15:45:06 +0100
parents 5c5908e81e93
children f0f06837a699
comparison
equal deleted inserted replaced
15333:37502e631202 15334:9d3d7b0f4861
1 *intro.txt* For Vim version 8.1. Last change: 2018 Jan 24 1 *intro.txt* For Vim version 8.1. Last change: 2019 Jan 01
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
50 This manual is a reference for all the Vim commands and options. This is not 50 This manual is a reference for all the Vim commands and options. This is not
51 an introduction to the use of Vi or Vim, it gets a bit complicated here and 51 an introduction to the use of Vi or Vim, it gets a bit complicated here and
52 there. For beginners, there is a hands-on |tutor|. To learn using Vim, read 52 there. For beginners, there is a hands-on |tutor|. To learn using Vim, read
53 the user manual |usr_toc.txt|. 53 the user manual |usr_toc.txt|.
54 54
55 *book* 55 *book* *books*
56 There are many books on Vi that contain a section for beginners. There are 56 Most books on Vi and Vim contain a section for beginners. Others are spending
57 two books I can recommend: 57 more words on specific functionality. You can find an overview of Vim books
58 58 here:
59 "Vim - Vi Improved" by Steve Oualline 59 http://iccf-holland.org/vim_books.html
60
61 This is the very first book completely dedicated to Vim. It is very good for
62 beginners. The most often used commands are explained with pictures and
63 examples. The less often used commands are also explained, the more advanced
64 features are summarized. There is a comprehensive index and a quick
65 reference. Parts of this book have been included in the user manual
66 |frombook|.
67 Published by New Riders Publishing. ISBN: 0735710015
68 For more information try one of these:
69 http://iccf-holland.org/click5.html
70 http://www.vim.org/iccf/click5.html
71
72 "Learning the Vi editor" by Linda Lamb and Arnold Robbins
73
74 This is a book about Vi that includes a chapter on Vim (in the sixth edition).
75 The first steps in Vi are explained very well. The commands that Vim adds are
76 only briefly mentioned. There is also a German translation.
77 Published by O'Reilly. ISBN: 1-56592-426-6.
78 60
79 ============================================================================== 61 ==============================================================================
80 2. Vim on the internet *internet* 62 2. Vim on the internet *internet*
81 63
82 *www* *WWW* *faq* *FAQ* *distribution* *download* 64 *www* *WWW* *faq* *FAQ* *distribution* *download*
83 The Vim pages contain the most recent information about Vim. They also 65 The Vim pages contain the most recent information about Vim. They also
84 contain links to the most recent version of Vim. The FAQ is a list of 66 contain links to the most recent version of Vim. The FAQ is a list of
85 Frequently Asked Questions. Read this if you have problems. 67 Frequently Asked Questions. Read this if you have problems.
86 68
87 Vim home page: http://www.vim.org/ 69 Vim home page: https://www.vim.org/
88 Vim FAQ: http://vimdoc.sf.net/ 70 Vim FAQ: https://vimhelp.appspot.com/vim_faq.txt.html
89 Downloading: ftp://ftp.vim.org/pub/vim/MIRRORS 71 Downloading: https://www.vim.org/download.php
90 72
91 73
92 Usenet News group where Vim is discussed: *news* *usenet* 74 Usenet News group where Vim is discussed: *news* *usenet*
93 comp.editors 75 comp.editors
94 This group is also for other editors. If you write about Vim, don't forget to 76 This group is also for other editors. If you write about Vim, don't forget to
112 Vim. 94 Vim.
113 95
114 See http://www.vim.org/maillist.php for the latest information. 96 See http://www.vim.org/maillist.php for the latest information.
115 97
116 NOTE: 98 NOTE:
99 - Anyone can see the archive, e.g. on Google groups. Search this if you have
100 questions.
117 - You can only send messages to these lists if you have subscribed! 101 - You can only send messages to these lists if you have subscribed!
102 - The first message is moderated, thus it may take a few hours to show up.
118 - You need to send the messages from the same location as where you subscribed 103 - You need to send the messages from the same location as where you subscribed
119 from (to avoid spam mail). 104 from (to avoid spam mail).
120 - Maximum message size is 40000 characters.
121 105
122 *subscribe-maillist* 106 *subscribe-maillist*
123 If you want to join, send a message to 107 If you want to join, send a message to
124 <vim-subscribe@vim.org> 108 <vim-subscribe@vim.org>
125 Make sure that your "From:" address is correct. Then the list server will 109 Make sure that your "From:" address is correct. Then the list server will
148 Preferably start Vim with: > 132 Preferably start Vim with: >
149 vim --clean -u reproduce.vim 133 vim --clean -u reproduce.vim
150 Where reproduce.vim is a script that reproduces the problem. Try different 134 Where reproduce.vim is a script that reproduces the problem. Try different
151 machines, if relevant (is this an MS-Windows specific bug perhaps?). 135 machines, if relevant (is this an MS-Windows specific bug perhaps?).
152 136
153 Send me patches if you can! 137 Send me patches if you can! If you create a pull request on
138 https://github.com/vim/vim then the automated checks will run and report any
139 obvious problems. But you can also send the patch by email (use an attachment
140 to avoid white space changes).
154 141
155 It will help to include information about the version of Vim you are using and 142 It will help to include information about the version of Vim you are using and
156 your setup. You can get the information with this command: > 143 your setup. You can get the information with this command: >
157 :so $VIMRUNTIME/bugreport.vim 144 :so $VIMRUNTIME/bugreport.vim
158 This will create a file "bugreport.txt" in the current directory, with a lot 145 This will create a file "bugreport.txt" in the current directory, with a lot
187 introduce Y2K problems, but those are not really part of Vim itself. 174 introduce Y2K problems, but those are not really part of Vim itself.
188 175
189 ============================================================================== 176 ==============================================================================
190 3. Credits *credits* *author* *Bram* *Moolenaar* 177 3. Credits *credits* *author* *Bram* *Moolenaar*
191 178
192 Most of Vim was written by Bram Moolenaar <Bram@vim.org>. 179 Most of Vim was created by Bram Moolenaar <Bram@vim.org>.
193 180
194 Parts of the documentation come from several Vi manuals, written by: 181 Parts of the documentation come from several Vi manuals, written by:
195 W.N. Joy 182 W.N. Joy
196 Alan P.W. Hewett 183 Alan P.W. Hewett
197 Mark Horton 184 Mark Horton
266 Stefan 'Sec' Zehl Maintainer of vim.org 253 Stefan 'Sec' Zehl Maintainer of vim.org
267 Yasuhiro Matsumoto many MS-Windows improvements 254 Yasuhiro Matsumoto many MS-Windows improvements
268 Ken Takata fixes and features 255 Ken Takata fixes and features
269 Kazunobu Kuriyama GTK 3 256 Kazunobu Kuriyama GTK 3
270 Christian Brabandt many fixes, features, user support, etc. 257 Christian Brabandt many fixes, features, user support, etc.
258 Yegappan Lakshmanan many quickfix features
271 259
272 I wish to thank all the people that sent me bug reports and suggestions. The 260 I wish to thank all the people that sent me bug reports and suggestions. The
273 list is too long to mention them all here. Vim would not be the same without 261 list is too long to mention them all here. Vim would not be the same without
274 the ideas from all these people: They keep Vim alive! 262 the ideas from all these people: They keep Vim alive!
275 *love* *peace* *friendship* *gross-national-happiness* 263 *love* *peace* *friendship* *gross-national-happiness*
298 *Elvis* 286 *Elvis*
299 Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't 287 Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't
300 as flexible as Vim. 288 as flexible as Vim.
301 The version used is 2.1. It is still being developed. Source code is 289 The version used is 2.1. It is still being developed. Source code is
302 freely available. 290 freely available.
291 *NeoVim*
292 NeoVim A Vim clone. Forked the Vim source in 2014 and went a different way.
293 Very much bound to github and has many more dependencies, making
294 development more complex and limiting portability. Code has been
295 refactored, resulting in patches not being exchangeable with Vim.
296 Supports a remote GUI and integration with scripting languages.
303 297
304 ============================================================================== 298 ==============================================================================
305 4. Notation *notation* 299 4. Notation *notation*
306 300
307 When syntax highlighting is used to read this, text that is not typed 301 When syntax highlighting is used to read this, text that is not typed