Lines Matching refs:can
57 You can use this to check which items have actually been defined. Quite
64 This also can be used to list clusters (explained in |44.8|). Just include
79 The ":syntax case" commands can appear anywhere in a syntax file and affect
82 contains both case-sensitive and non-case-sensitive elements, however, you can
94 can assign colors to a {group}. The {keyword} argument is an actual keyword.
132 The x language allows for abbreviations. For example, "next" can be
133 abbreviated to "n", "ne" or "nex". You can define them by using this command:
156 You can use any other character, like a plus or a quote.
163 Since you can use any search pattern, you can highlight very complex things
210 In the first line, the "contained" argument tells Vim that this keyword can
221 contain other code blocks. This can be defined this way: >
251 can have a comment on a preprocessor line, the preprocessor definition
275 You can use the contains argument to specify that everything can be contained.
282 You can specify that some groups are not contained. Thus contain all
287 With the "TOP" item you can include all items that don't have a "contained"
300 highlighting. This is how you can do this: >
306 The "nextgroup" argument specifies which item can come next. This is not
332 Suppose, that you want to highlight the parentheses differently. You can do
333 this with a lot of convoluted region statements, or you can use the
353 differently from the () text after a "for". In both of these there can be
363 Now you can give cWhile and cFor different highlighting. The cCondNest item
364 can appear in either of them, but take over the highlighting of the item it is
378 "if". But you don't want to include the "if" or the ( and ). You can do this
433 In this case, this is what you want. If it is not what you want, you can call
472 Their names start with @. Thus, you can define the three groups like this: >
478 You can add new group names to this cluster with the "add" argument: >
482 You can remove syntax groups from this list as well: >
490 want to write two syntax files, you can have the C++ syntax file read in the
499 After loading the C syntax items the specific C++ items can be defined.
543 You can tune this processing with some arguments. The "minlines" argument
555 To make synchronizing go a bit faster, tell Vim which syntax items can be
557 displaying text can be given the "display" argument.
559 syntax group. If you want to color things another way, you can specify a
564 If your programming language does not have C-style comments in it, you can try
571 A large "minlines" value can make Vim slower, especially when scrolling
573 Finally, you can specify a syntax group to look for by using this command:
600 You also can define matches and regions that are with no "grouphere" or
624 explain how the filetype can be detected. With a bit of luck your file will
631 syntax file works, but is missing some items, you can add items in a separate
693 For the linking use "hi def link", so that the user can select different