Lines Matching refs:that
30 Note that quite a few items are contradicting. This is intentional. A
47 - Vim will have a lot of features that Vi doesn't have. Going back from Vim
65 hard time finding and remembering them. Keep in mind that more commands and
67 - A feature that people do not know about is a useless feature. Don't add
68 obscure features, or at least add hints in documentation that they exist.
72 - There is no limit to the features that can be added. Selecting new features
81 and clear-screen. Commands should only use key strokes that most keyboards
83 - Support many platforms. A condition is that there is someone willing to do
84 Vim development on that platform, and it doesn't mean messing up the code.
89 as possible with a reasonable effort. Try to avoid that users must switch
98 - A feature that isn't documented is a useless feature. A patch for a new
102 - Don't make the text unnecessarily long. Less documentation means that an
115 - Don't forget that some people use Vim over a slow connection. Minimize the
117 - Items that add considerably to the size and are not used by many people
118 should be a feature that can be disabled.
140 defaults are carefully chosen such that most users will enjoy using Vim as it
149 this over an ssh connection. But if you don't need a text editor with that
152 everything but the kitchen sink, but some people say that you can clean one
156 - Vim is not a fancy GUI editor that tries to look nice at the cost of
181 github, but it's the diff that matters.
199 Traditionally Vim uses /* comments */. We intend to keep it that way
205 For new code or lines of code that change, it is preferred to use // comments.
232 Some functions that are common to use, have a special Vim version. Always
255 Because of the requirement that Vim runs on as many systems as possible, we
256 need to avoid using names that are already defined by the system. This is a
257 list of names that are known to cause trouble. The name is given as a regexp
316 Some compilers can't handle that and complain that "HAVE_SOME" is not defined.
445 have one window that shows the text with function bodies folded, another
446 window that shows a function body.
457 To avoid confusion, other items that are sometimes called window have been
473 was that none of them provided sufficient capabilities to be used as the spell
477 so that more than one language can be used in the same file.
482 - Performance: A few tests showed that it's possible to check spelling on the
485 The affix compression that most spell checkers use makes it slower too.
488 would be relatively simple, but that's not good enough). And performance
514 was that a trie (a kind of tree structure) is ideal for this. Both for
516 inserting a character only characters that lead to good words need to be
518 every position in the word. Also, a hashtable has the requirement that word
524 as "daktonerie". The number of changes that the first method would need to
525 try is very big, it's hard to find the good word that way. After soundfolding
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
547 before soundfolding it, which means that mistakes at the start and/or end
563 Also, it would be nice to prefer words that are already in the text. This way
564 the words that appear in the specific text are preferred for suggestions.
566 What has been implemented is to count words that have been seen during
568 initialized from words listed in COMMON items in the affix file, so that it
585 Note that some compilers cannot handle long lines or strings. The C89