mirror of
https://github.com/neovim/neovim.git
synced 2024-12-24 13:15:09 -07:00
doc: merge sponsor.txt into intro.txt
Also mention how to donate to Nvim. closes #8603
This commit is contained in:
parent
f679abef3e
commit
2ee4ce0639
@ -162,12 +162,8 @@ In WinDbg: choose Open Crash Dump on the File menu. Follow the instructions in
|
|||||||
*get-ms-debuggers*
|
*get-ms-debuggers*
|
||||||
3.5 Obtaining Microsoft Debugging Tools ~
|
3.5 Obtaining Microsoft Debugging Tools ~
|
||||||
|
|
||||||
The Debugging Tools for Windows (including WinDbg) can be downloaded from
|
Visual Studio 2017 Community Edition can be downloaded for free from:
|
||||||
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
|
https://visualstudio.microsoft.com/downloads/
|
||||||
This includes the WinDbg debugger.
|
|
||||||
|
|
||||||
Visual C++ 2005 Express Edition can be downloaded for free from:
|
|
||||||
http://msdn.microsoft.com/vstudio/express/visualC/default.aspx
|
|
||||||
|
|
||||||
=========================================================================
|
=========================================================================
|
||||||
vim:tw=78:ts=8:noet:ft=help:norl:
|
vim:tw=78:ts=8:noet:ft=help:norl:
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
*intro.txt* Nvim
|
*intro.txt* Nvim
|
||||||
|
|
||||||
|
|
||||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
NVIM REFERENCE MANUAL
|
||||||
|
|
||||||
|
|
||||||
Introduction to Vim *ref* *reference*
|
Introduction to Vim *ref* *reference*
|
||||||
@ -9,7 +9,7 @@ Introduction to Vim *ref* *reference*
|
|||||||
Type |gO| to see the table of contents.
|
Type |gO| to see the table of contents.
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
1. Introduction *intro*
|
Introduction *intro*
|
||||||
|
|
||||||
Vim stands for Vi IMproved. It used to be Vi IMitation, but there are so many
|
Vim stands for Vi IMproved. It used to be Vi IMitation, but there are so many
|
||||||
improvements that a name change was appropriate. Vim is a text editor which
|
improvements that a name change was appropriate. Vim is a text editor which
|
||||||
@ -28,8 +28,8 @@ is not located in the default place. You can jump to subjects like with tags:
|
|||||||
Use CTRL-] to jump to a subject under the cursor, use CTRL-T to jump back.
|
Use CTRL-] to jump to a subject under the cursor, use CTRL-T to jump back.
|
||||||
|
|
||||||
*pronounce*
|
*pronounce*
|
||||||
Vim is pronounced as one word, like Jim, not vi-ai-em. It's written with a
|
Vim is pronounced as one word, like Jim. Nvim is pronounced as N-vim, or,
|
||||||
capital, since it's a name, again like Jim.
|
continuing with the Jim simile, N-Jim, which sounds like Ninja.
|
||||||
|
|
||||||
This manual is a reference for all the Vim commands and options. This is not
|
This manual is a reference for all the Vim commands and options. This is not
|
||||||
an introduction to the use of Vi or Vim, it gets a bit complicated here and
|
an introduction to the use of Vi or Vim, it gets a bit complicated here and
|
||||||
@ -37,134 +37,67 @@ there. For beginners, there is a hands-on |tutor|. To learn using Vim, read
|
|||||||
the user manual |usr_toc.txt|.
|
the user manual |usr_toc.txt|.
|
||||||
|
|
||||||
*book*
|
*book*
|
||||||
There are many books on Vi that contain a section for beginners. There are
|
There are many books on Vi and Vim. We recommend these books:
|
||||||
two books I can recommend:
|
|
||||||
|
"Practical Vim" by Drew Neil
|
||||||
|
"Modern Vim" by Drew Neil
|
||||||
|
https://vimcasts.org/publications/
|
||||||
|
|
||||||
|
"Practical Vim" is a popular because of its focus on quickly learning common
|
||||||
|
editing tasks with Vim. "Modern Vim" explores new features introduced by Nvim
|
||||||
|
and Vim 8.
|
||||||
|
|
||||||
"Vim - Vi Improved" by Steve Oualline
|
"Vim - Vi Improved" by Steve Oualline
|
||||||
|
|
||||||
This is the very first book completely dedicated to Vim. It is very good for
|
This is the first book dedicated to Vim. Parts of it were included in the
|
||||||
beginners. The most often used commands are explained with pictures and
|
user manual. |frombook| ISBN: 0735710015
|
||||||
examples. The less often used commands are also explained, the more advanced
|
|
||||||
features are summarized. There is a comprehensive index and a quick
|
|
||||||
reference. Parts of this book have been included in the user manual
|
|
||||||
|frombook|.
|
|
||||||
Published by New Riders Publishing. ISBN: 0735710015
|
|
||||||
For more information try one of these:
|
For more information try one of these:
|
||||||
http://iccf-holland.org/click5.html
|
https://iccf-holland.org/click5.html
|
||||||
http://www.vim.org/iccf/click5.html
|
https://www.vim.org/iccf/click5.html
|
||||||
|
|
||||||
"Learning the Vi editor" by Linda Lamb and Arnold Robbins
|
|
||||||
|
|
||||||
This is a book about Vi that includes a chapter on Vim (in the sixth edition).
|
|
||||||
The first steps in Vi are explained very well. The commands that Vim adds are
|
|
||||||
only briefly mentioned. There is also a German translation.
|
|
||||||
Published by O'Reilly. ISBN: 1-56592-426-6.
|
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
2. Vim on the internet *internet*
|
Nvim on the interwebs *internet*
|
||||||
|
|
||||||
*www* *WWW* *faq* *FAQ* *distribution* *download*
|
*www* *WWW* *faq* *FAQ* *distribution* *download*
|
||||||
The Vim pages contain the most recent information about Vim. They also
|
|
||||||
contain links to the most recent version of Vim. The FAQ is a list of
|
|
||||||
Frequently Asked Questions. Read this if you have problems.
|
|
||||||
|
|
||||||
Vim home page: http://www.vim.org/
|
Nvim home page: https://neovim.io/
|
||||||
Vim FAQ: http://vimdoc.sf.net/
|
Nvim FAQ: https://github.com/neovim/neovim/wiki/FAQ
|
||||||
Downloading: ftp://ftp.vim.org/pub/vim/MIRRORS
|
Downloads: https://github.com/neovim/neovim/releases
|
||||||
|
Vim FAQ: https://vimhelp.appspot.com/vim_faq.txt.html
|
||||||
|
Vim home page: https://www.vim.org/
|
||||||
Usenet News group where Vim is discussed: *news* *usenet*
|
|
||||||
comp.editors
|
|
||||||
This group is also for other editors. If you write about Vim, don't forget to
|
|
||||||
mention that.
|
|
||||||
|
|
||||||
*mail-list* *maillist*
|
|
||||||
There are several mailing lists for Vim:
|
|
||||||
<vim@vim.org> *vim-use* *vim_use*
|
|
||||||
For discussions about using existing versions of Vim: Useful mappings,
|
|
||||||
questions, answers, where to get a specific version, etc. There are
|
|
||||||
quite a few people watching this list and answering questions, also
|
|
||||||
for beginners. Don't hesitate to ask your question here.
|
|
||||||
<vim-dev@vim.org> *vim-dev* *vim_dev* *vimdev*
|
|
||||||
For discussions about changing Vim: New features, porting, patches,
|
|
||||||
beta-test versions, etc.
|
|
||||||
<vim-announce@vim.org> *vim-announce* *vim_announce*
|
|
||||||
Announcements about new versions of Vim; also for beta-test versions
|
|
||||||
and ports to different systems. This is a read-only list.
|
|
||||||
<vim-mac@vim.org> *vim-mac* *vim_mac*
|
|
||||||
For discussions about using and improving the Macintosh version of
|
|
||||||
Vim.
|
|
||||||
|
|
||||||
See http://www.vim.org/maillist.php for the latest information.
|
|
||||||
|
|
||||||
NOTE:
|
|
||||||
- You can only send messages to these lists if you have subscribed!
|
|
||||||
- You need to send the messages from the same location as where you subscribed
|
|
||||||
from (to avoid spam mail).
|
|
||||||
- Maximum message size is 40000 characters.
|
|
||||||
|
|
||||||
*subscribe-maillist*
|
|
||||||
If you want to join, send a message to
|
|
||||||
<vim-subscribe@vim.org>
|
|
||||||
Make sure that your "From:" address is correct. Then the list server will
|
|
||||||
give you help on how to subscribe.
|
|
||||||
|
|
||||||
*maillist-archive*
|
|
||||||
For more information and archives look on the Vim maillist page:
|
|
||||||
http://www.vim.org/maillist.php
|
|
||||||
|
|
||||||
|
|
||||||
Bug reports: *bugs* *bug-reports* *bugreport.vim*
|
Bug reports: *bugs* *bug-reports* *bugreport.vim*
|
||||||
|
|
||||||
Report bugs on GitHub: https://github.com/neovim/neovim/issues
|
Report bugs on GitHub: https://github.com/neovim/neovim/issues
|
||||||
|
|
||||||
Please be brief; all the time that is spent on answering mail is subtracted
|
Be brief, yet complete. Always give a reproducible example and try to find
|
||||||
from the time that is spent on improving Vim! Always give a reproducible
|
out which settings or other things trigger the bug.
|
||||||
example and try to find out which settings or other things trigger the bug.
|
|
||||||
|
|
||||||
Preferably start Vim with: >
|
If Nvim crashes, try to get a backtrace. See |debug.txt|.
|
||||||
vim --clean -u reproduce.vim
|
|
||||||
Where reproduce.vim is a script that reproduces the problem. Try different
|
|
||||||
machines, if relevant (is this an MS-Windows specific bug perhaps?).
|
|
||||||
|
|
||||||
Send me patches if you can!
|
|
||||||
|
|
||||||
It will help to include information about the version of Vim you are using and
|
|
||||||
your setup. You can get the information with this command: >
|
|
||||||
:so $VIMRUNTIME/bugreport.vim
|
|
||||||
This will create a file "bugreport.txt" in the current directory, with a lot
|
|
||||||
of information of your environment. Before sending this out, check if it
|
|
||||||
doesn't contain any confidential information!
|
|
||||||
|
|
||||||
If Vim crashes, please try to find out where. You can find help on this here:
|
|
||||||
|debug.txt|.
|
|
||||||
|
|
||||||
In case of doubt or when you wonder if the problem has already been fixed but
|
|
||||||
you can't find a fix for it, become a member of the vim-dev maillist and ask
|
|
||||||
your question there. |maillist|
|
|
||||||
|
|
||||||
*year-2000* *Y2K*
|
|
||||||
Since Vim internally doesn't use dates for editing, there is no year 2000
|
|
||||||
problem to worry about. Vim does use the time in the form of seconds since
|
|
||||||
January 1st 1970. It is used for a time-stamp check of the edited file and
|
|
||||||
the swap file, which is not critical and should only cause warning messages.
|
|
||||||
|
|
||||||
There might be a year 2038 problem, when the seconds don't fit in a 32 bit int
|
|
||||||
anymore. This depends on the compiler, libraries and operating system.
|
|
||||||
Specifically, time_t and the ctime() function are used. And the time_t is
|
|
||||||
stored in four bytes in the swap file. But that's only used for printing a
|
|
||||||
file date/time for recovery, it will never affect normal editing.
|
|
||||||
|
|
||||||
The Vim strftime() function directly uses the strftime() system function.
|
|
||||||
localtime() uses the time() system function. getftime() uses the time
|
|
||||||
returned by the stat() system function. If your system libraries are year
|
|
||||||
2000 compliant, Vim is too.
|
|
||||||
|
|
||||||
The user may create scripts for Vim that use external commands. These might
|
|
||||||
introduce Y2K problems, but those are not really part of Vim itself.
|
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
3. Credits *credits* *author* *Bram* *Moolenaar*
|
Sponsor Vim/Nvim development *sponsor* *register*
|
||||||
|
|
||||||
|
Fixing bugs and adding new features takes a lot of time and effort. To show
|
||||||
|
your appreciation for the work and motivate Bram and others to continue
|
||||||
|
working on Vim please send a donation.
|
||||||
|
|
||||||
|
Since Bram is back to a paid job the money will now be used to help children
|
||||||
|
in Uganda. See |uganda|. But at the same time donations increase Bram's
|
||||||
|
motivation to keep working on Vim!
|
||||||
|
|
||||||
|
For the most recent information about sponsoring look on the Vim web site:
|
||||||
|
|
||||||
|
https://www.vim.org/sponsor/
|
||||||
|
|
||||||
|
|
||||||
|
Neovim development is funded separately from Vim:
|
||||||
|
|
||||||
|
https://neovim.io/sponsors/
|
||||||
|
|
||||||
|
==============================================================================
|
||||||
|
Credits *credits* *author* *Bram* *Moolenaar*
|
||||||
|
|
||||||
Most of Vim was written by Bram Moolenaar <Bram@vim.org>.
|
Most of Vim was written by Bram Moolenaar <Bram@vim.org>.
|
||||||
|
|
||||||
@ -273,7 +206,7 @@ Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't
|
|||||||
freely available.
|
freely available.
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
4. Notation *notation*
|
Notation *notation*
|
||||||
|
|
||||||
When syntax highlighting is used to read this, text that is not typed
|
When syntax highlighting is used to read this, text that is not typed
|
||||||
literally is often highlighted with the Special group. These are items in [],
|
literally is often highlighted with the Special group. These are items in [],
|
||||||
@ -494,7 +427,7 @@ examples and use them directly. Or type them literally, including the '<' and
|
|||||||
":autocmd"!
|
":autocmd"!
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
5. Modes, introduction *vim-modes-intro* *vim-modes*
|
Modes, introduction *vim-modes-intro* *vim-modes*
|
||||||
|
|
||||||
Vim has seven BASIC modes:
|
Vim has seven BASIC modes:
|
||||||
|
|
||||||
@ -579,7 +512,7 @@ Insert Select mode Entered when starting Select mode from Insert mode.
|
|||||||
is shown at the bottom of the window.
|
is shown at the bottom of the window.
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
6. Switching from mode to mode *mode-switching*
|
Switching from mode to mode *mode-switching*
|
||||||
|
|
||||||
If for any reason you do not know which mode you are in, you can always get
|
If for any reason you do not know which mode you are in, you can always get
|
||||||
back to Normal mode by typing <Esc> twice. This doesn't work for Ex mode
|
back to Normal mode by typing <Esc> twice. This doesn't work for Ex mode
|
||||||
@ -650,7 +583,7 @@ Q or gQ Switch to Ex mode. This is like typing ":" commands
|
|||||||
Use the ":vi" command |:visual| to exit this mode.
|
Use the ":vi" command |:visual| to exit this mode.
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
7. The window contents *window-contents*
|
The window contents *window-contents*
|
||||||
|
|
||||||
In Normal mode and Insert/Replace mode the screen window will show the current
|
In Normal mode and Insert/Replace mode the screen window will show the current
|
||||||
contents of the buffer: What You See Is What You Get. There are two
|
contents of the buffer: What You See Is What You Get. There are two
|
||||||
@ -773,7 +706,7 @@ On most Unix systems, resizing the window is recognized and handled correctly
|
|||||||
by Vim.
|
by Vim.
|
||||||
|
|
||||||
==============================================================================
|
==============================================================================
|
||||||
8. Definitions *definitions*
|
Definitions *definitions*
|
||||||
|
|
||||||
buffer Contains lines of text, usually read from a file.
|
buffer Contains lines of text, usually read from a file.
|
||||||
screen The whole area that Vim uses to work in. This can be
|
screen The whole area that Vim uses to work in. This can be
|
||||||
|
@ -1,216 +0,0 @@
|
|||||||
*sponsor.txt* Nvim
|
|
||||||
|
|
||||||
|
|
||||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
SPONSOR VIM DEVELOPMENT *sponsor*
|
|
||||||
|
|
||||||
Fixing bugs and adding new features takes a lot of time and effort. To show
|
|
||||||
your appreciation for the work and motivate Bram and others to continue
|
|
||||||
working on Vim please send a donation.
|
|
||||||
|
|
||||||
Since Bram is back to a paid job the money will now be used to help children
|
|
||||||
in Uganda. See |uganda|. But at the same time donations increase Bram's
|
|
||||||
motivation to keep working on Vim!
|
|
||||||
|
|
||||||
For the most recent information about sponsoring look on the Vim web site:
|
|
||||||
|
|
||||||
http://www.vim.org/sponsor/
|
|
||||||
|
|
||||||
More explanations can be found in the |sponsor-faq|.
|
|
||||||
|
|
||||||
|
|
||||||
REGISTERED VIM USER *register*
|
|
||||||
|
|
||||||
You can become a registered Vim user by sending at least 10 euro. This works
|
|
||||||
similar to sponsoring Vim, see |sponsor| above. Registration was made
|
|
||||||
possible for the situation where your boss or bookkeeper may be willing to
|
|
||||||
register software, but does not like the terms "sponsoring" and "donation".
|
|
||||||
|
|
||||||
More explanations can be found in the |register-faq|.
|
|
||||||
|
|
||||||
|
|
||||||
VOTE FOR FEATURES *vote-for-features*
|
|
||||||
|
|
||||||
To give registered Vim users and sponsors an advantage over lurkers they can
|
|
||||||
vote for the items Bram should work on. How does this voting work?
|
|
||||||
|
|
||||||
1. You send at least 10 euro. See below for ways to transfer money
|
|
||||||
|send-money|.
|
|
||||||
|
|
||||||
2. You will be e-mailed a registration key. Enter this key on your account
|
|
||||||
page on the Vim website. You can easily create an account if you don't
|
|
||||||
have one yet.
|
|
||||||
|
|
||||||
3. You can enter your votes on the voting page. There is a link to that page
|
|
||||||
on your account page after entering a registration key. Your votes will
|
|
||||||
be counted for two years.
|
|
||||||
|
|
||||||
4. The voting results appear on the results page, which is visible for
|
|
||||||
everybody: http://www.vim.org/sponsor/vote_results.php
|
|
||||||
|
|
||||||
Additionally, once you have sent 100 euro or more in total, your name appears
|
|
||||||
in the "Vim hall of honour": http://www.vim.org/sponsor/hall_of_honour.php
|
|
||||||
But only if you enable this on your account page.
|
|
||||||
|
|
||||||
|
|
||||||
HOW TO SEND MONEY *send-money*
|
|
||||||
|
|
||||||
Credit card Through PayPal, see the PayPal site for information:
|
|
||||||
https://www.paypal.com/en_US/mrb/pal=XAC62PML3GF8Q
|
|
||||||
The e-mail address for sending sponsorship money is:
|
|
||||||
donate@vim.org
|
|
||||||
The e-mail address for Vim registration is:
|
|
||||||
register@vim.org
|
|
||||||
Using Euro is preferred, other currencies are also accepted.
|
|
||||||
In Euro countries a bank transfer is preferred, this has lower
|
|
||||||
costs.
|
|
||||||
|
|
||||||
Other methods See |iccf-donations|.
|
|
||||||
Include "Vim sponsor" or "Vim registration" in the comment of
|
|
||||||
your money transfer. Send me an e-mail that mentions the
|
|
||||||
amount you transferred if you want to vote for features and
|
|
||||||
show others you are a registered Vim user or sponsor.
|
|
||||||
|
|
||||||
Cash Small amounts can be sent with ordinary mail. Put something
|
|
||||||
around the money, so that it's not noticeable from the
|
|
||||||
outside. Mention your e-mail address if you want to vote for
|
|
||||||
features and show others you are a registered Vim user or
|
|
||||||
sponsor.
|
|
||||||
|
|
||||||
You can use this permanent address:
|
|
||||||
Bram Moolenaar
|
|
||||||
Finsterruetihof 1
|
|
||||||
8134 Adliswil
|
|
||||||
Switzerland
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
QUESTIONS AND ANSWERS *sponsor-faq* *register-faq*
|
|
||||||
|
|
||||||
Why should I give money?
|
|
||||||
|
|
||||||
If you do not show your appreciation for Vim then Bram will be less motivated
|
|
||||||
to fix bugs and add new features. He will do something else instead.
|
|
||||||
|
|
||||||
|
|
||||||
How much money should I send?
|
|
||||||
|
|
||||||
That is up to you. The more you give, the more children will be helped.
|
|
||||||
An indication for individuals that use Vim at home: 10 Euro per year. For
|
|
||||||
professional use: 30 Euro per year per person. Send at least 10 euro to be
|
|
||||||
able to vote for features.
|
|
||||||
|
|
||||||
|
|
||||||
What do I get in return?
|
|
||||||
|
|
||||||
Each registered Vim user and sponsor who donates at least 10 euro will be able
|
|
||||||
to vote for new features. These votes will give priority to the work on Vim.
|
|
||||||
The votes are valid for two years. The more money you send the more your
|
|
||||||
votes count |votes-counted|.
|
|
||||||
|
|
||||||
If you send 100 Euro or more in total you will be mentioned on the "Vim hall
|
|
||||||
of honour" page on the Vim web site. But only if you enable this on your
|
|
||||||
account page. You can also select whether the amount will be visible.
|
|
||||||
|
|
||||||
|
|
||||||
How do I become a Vim sponsor or registered Vim user?
|
|
||||||
|
|
||||||
Send money, as explained above |send-money| and include your e-mail address.
|
|
||||||
When the money has been received you will receive a unique registration key.
|
|
||||||
This key can be used on the Vim website to activate voting on your Vim
|
|
||||||
account. You will then get an extra page where you can vote for features and
|
|
||||||
choose whether others will be able to see that you donated. There is a link
|
|
||||||
to this page on your "My Account" page.
|
|
||||||
|
|
||||||
|
|
||||||
What is the difference between sponsoring and registering?
|
|
||||||
|
|
||||||
It has a different name. Use the term "registration" if your boss doesn't
|
|
||||||
like "sponsoring" or "donation". The benefits are the same.
|
|
||||||
|
|
||||||
|
|
||||||
How can I send money?
|
|
||||||
|
|
||||||
See |send-money|. Check the web site for the most recent information:
|
|
||||||
http://www.vim.org/sponsor/
|
|
||||||
|
|
||||||
|
|
||||||
Why don't you use the SourceForge donation system?
|
|
||||||
|
|
||||||
SourceForge takes 5% of the donations for themselves. If you want to support
|
|
||||||
SourceForge you can send money to them directly.
|
|
||||||
|
|
||||||
|
|
||||||
I cannot afford to send money, may I still use Vim?
|
|
||||||
|
|
||||||
Yes.
|
|
||||||
|
|
||||||
|
|
||||||
I did not register Vim, can I use all available features?
|
|
||||||
|
|
||||||
Yes.
|
|
||||||
|
|
||||||
|
|
||||||
I noticed a bug, do I need to register before I can report it?
|
|
||||||
|
|
||||||
No, suggestions for improving Vim can always be given. For improvements use
|
|
||||||
the developer |maillist|, for reporting bugs see |bugs|.
|
|
||||||
|
|
||||||
|
|
||||||
How are my votes counted? *votes-counted*
|
|
||||||
|
|
||||||
You may vote when you send 10 euro or more. You can enter up to ten votes.
|
|
||||||
You can select the same item several times to give it more points. You can
|
|
||||||
also enter three counter votes, these count as negative points.
|
|
||||||
|
|
||||||
When you send 30 euro or more the points are doubled. Above 100 euro they
|
|
||||||
count four times, above 300 euro they count six times, above 1000 euro ten
|
|
||||||
times.
|
|
||||||
|
|
||||||
|
|
||||||
Can I change my votes?
|
|
||||||
|
|
||||||
You can change your votes any time you like, up to two years after you
|
|
||||||
sent money. The points will be counted right away.
|
|
||||||
|
|
||||||
|
|
||||||
Can I add an item to vote on?
|
|
||||||
|
|
||||||
Not directly. You can suggest items to vote on to Bram. He will consider
|
|
||||||
fitting your item into the list.
|
|
||||||
|
|
||||||
|
|
||||||
How about Charityware?
|
|
||||||
|
|
||||||
Currently the Vim donations go to |uganda| anyway. Thus it doesn't matter if
|
|
||||||
you sponsor Vim or ICCF. Except that Vim sponsoring will allow you to vote
|
|
||||||
for features.
|
|
||||||
|
|
||||||
|
|
||||||
I donated $$$, now please add feature XYZ!
|
|
||||||
|
|
||||||
There is no direct relation between your donation and the work Bram does.
|
|
||||||
Otherwise you would be paying for work and we would have to pay tax over the
|
|
||||||
donation. If you want to hire Bram for specific work, contact him directly,
|
|
||||||
don't use the donation system.
|
|
||||||
|
|
||||||
|
|
||||||
Are the donations tax deductible?
|
|
||||||
|
|
||||||
That depends on your country. The donations to help the children in |Uganda|
|
|
||||||
are tax deductible in Holland, Germany, Canada and in the USA. See the ICCF
|
|
||||||
website http://iccf-holland.org/donate.html. You must send an e-mail to Bram
|
|
||||||
to let him know that the donation is done because of the use of Vim.
|
|
||||||
|
|
||||||
|
|
||||||
Can you send me a bill?
|
|
||||||
|
|
||||||
No, because there is no relation between the money you send and the work that
|
|
||||||
is done. But a receipt is possible.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
vim:tw=78:ts=8:noet:ft=help:norl:
|
|
@ -68,9 +68,9 @@ For more info see |vimrc|.
|
|||||||
==============================================================================
|
==============================================================================
|
||||||
*01.3* Using the Vim tutor *tutor* *vimtutor*
|
*01.3* Using the Vim tutor *tutor* *vimtutor*
|
||||||
|
|
||||||
Instead of reading the text (boring!) you can use the vimtutor to learn your
|
Instead of reading the text (boring!) you can use :Tutor to learn your first
|
||||||
first Vim commands. This is a 30 minute tutorial that teaches the most basic
|
Vim commands. This is a 30 minute tutorial that teaches the most basic Vim
|
||||||
Vim functionality hands-on.
|
functionality hands-on.
|
||||||
|
|
||||||
To start the tutorial, execute >
|
To start the tutorial, execute >
|
||||||
|
|
||||||
|
@ -149,8 +149,8 @@ preprocess_patch() {
|
|||||||
local na_src='proto\|Make*\|gui_*\|if_lua\|if_mzsch\|if_olepp\|if_ole\|if_perl\|if_py\|if_ruby\|if_tcl\|if_xcmdsrv'
|
local na_src='proto\|Make*\|gui_*\|if_lua\|if_mzsch\|if_olepp\|if_ole\|if_perl\|if_py\|if_ruby\|if_tcl\|if_xcmdsrv'
|
||||||
2>/dev/null $nvim --cmd 'set dir=/tmp' +'g@^diff --git a/src/\S*\<\%(testdir/\)\@<!\%('${na_src}'\)@norm! d/\v(^diff)|%$
' +w +q "$file"
|
2>/dev/null $nvim --cmd 'set dir=/tmp' +'g@^diff --git a/src/\S*\<\%(testdir/\)\@<!\%('${na_src}'\)@norm! d/\v(^diff)|%$
' +w +q "$file"
|
||||||
|
|
||||||
# Remove channel.txt, netbeans.txt, os_*.txt, term.txt, todo.txt, version*.txt, tags
|
# Remove unwanted Vim doc files.
|
||||||
local na_doc='channel\.txt\|netbeans\.txt\|os_\w\+\.txt\|term\.txt\|todo\.txt\|version\d\.txt\|tags'
|
local na_doc='channel\.txt\|netbeans\.txt\|os_\w\+\.txt\|term\.txt\|todo\.txt\|version\d\.txt\|sponsor\.txt\|intro\.txt\|tags'
|
||||||
2>/dev/null $nvim --cmd 'set dir=/tmp' +'g@^diff --git a/runtime/doc/\<\%('${na_doc}'\)\>@norm! d/\v(^diff)|%$
' +w +q "$file"
|
2>/dev/null $nvim --cmd 'set dir=/tmp' +'g@^diff --git a/runtime/doc/\<\%('${na_doc}'\)\>@norm! d/\v(^diff)|%$
' +w +q "$file"
|
||||||
|
|
||||||
# Remove "Last change ..." changes in doc files.
|
# Remove "Last change ..." changes in doc files.
|
||||||
|
Loading…
Reference in New Issue
Block a user