Lines Matching refs:be
9 This text is important for those who want to be involved in further developing
31 balance must be found between them.
36 First of all, it should be possible to use Vim as a drop-in replacement for
37 Vi. When the user wants to, Vim can be used in compatible mode and hardly
38 any differences with the original Vi will be noticed.
48 to Vi will be a problem, this cannot be avoided.
50 crashing, etc.). Those will only be included when someone has a good reason
51 why it should be included and it's not too much work.
52 - For some items it is debatable whether Vi compatibility should be
53 maintained. There will be an option flag for these.
66 options will be added later.
72 - There is no limit to the features that can be added. Selecting new features
88 version. Features should be present in all versions, or at least in as many
92 platform, does not mean it cannot be implemented. [This intentionally
93 contradicts the previous item, these two must be balanced.]
100 - Documentation should be comprehensive and understandable. Using examples is
108 Using Vim must not be a big attack on system resources. Keep it small and
112 - Many users start Vim from a shell very often. Startup time must be short.
113 - Commands must work efficiently. The time they consume must be as small as
118 should be a feature that can be disabled.
125 - The source code should not become a mess. It should be reliable code.
129 - Porting to another platform should be made easy, without having to change
138 than coercing its users into particular patterns of work. This can be for
141 is. Commands and options can be used to adjust Vim to the desire of the user
148 window, in which you can run a shell or debugger. E.g. to be able to do
154 To use Vim with gdb see |terminal-debugger|. Other (older) tools can be
173 version in sync with the main code base (it may be a while before your
174 changes will be included). You do need to spend some time learning git,
215 "long long" is allowed and can be expected to be 64 bits. Use %lld in printf
218 Not to be used ~
220 These C99 features are not to be used, because not enough compilers support
223 declarations need to be at the start of the block.
251 Function names can not be more than 31 characters long (because of VMS).
307 Define'ed names should be uppercase: >
362 When a block has one line the braces can be left out. When an if/else has
444 Several forms of folding should be possible for the same buffer. For example,
464 window View on a buffer. There can be several windows in Vim,
471 When spell checking was going to be added to Vim a survey was done over the
473 was that none of them provided sufficient capabilities to be used as the spell
476 - Missing support for multibyte encodings. At least UTF-8 must be supported,
477 so that more than one language can be used in the same file.
487 have to be setup. That's complicated to do in a portable way (Unix-only
488 would be relatively simple, but that's not good enough). And performance
496 and could be a misspelled often-used word.
498 another program or library would be acceptable. But the word lists probably
499 differ, the suggestions may be wrong words.
516 inserting a character only characters that lead to good words need to be
523 know how it is spelled. For example, the word "dictionary" might be written
535 seconds for English, which can be acceptable for interactive use. But for
539 2. Use a trie for the soundfolded words, so that searching can be done just
546 does. Disadvantage is that affixes need to be stripped from the bad word
562 And maintaining the word frequency for all languages will be a heavy task.
563 Also, it would be nice to prefer words that are already in the text. This way
581 int 32 or 64 bit signed (16 might be possible with limited features)