Bram Moolenaar | eb49041 | 2022-06-28 13:44:46 +0100 | [diff] [blame] | 1 | *textprop.txt* For Vim version 9.0. Last change: 2021 Nov 23 |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 2 | |
| 3 | |
| 4 | VIM REFERENCE MANUAL by Bram Moolenaar |
| 5 | |
| 6 | |
Bram Moolenaar | a6c27c4 | 2019-05-09 19:16:22 +0200 | [diff] [blame] | 7 | Displaying text with properties attached. *textprop* *text-properties* |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 8 | |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 9 | |
| 10 | 1. Introduction |text-prop-intro| |
| 11 | 2. Functions |text-prop-functions| |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 12 | 3. When text changes |text-prop-changes| |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 13 | |
| 14 | |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 15 | {not able to use text properties when the |+textprop| feature was |
| 16 | disabled at compile time} |
| 17 | |
| 18 | ============================================================================== |
| 19 | 1. Introduction *text-prop-intro* |
| 20 | |
| 21 | Text properties can be attached to text in a buffer. They will move with the |
| 22 | text: If lines are deleted or inserted the properties move with the text they |
| 23 | are attached to. Also when inserting/deleting text in the line before the |
| 24 | text property. And when inserting/deleting text inside the text property, it |
| 25 | will increase/decrease in size. |
| 26 | |
| 27 | The main use for text properties is to highlight text. This can be seen as a |
| 28 | replacement for syntax highlighting. Instead of defining patterns to match |
| 29 | the text, the highlighting is set by a script, possibly using the output of an |
| 30 | external parser. This only needs to be done once, not every time when |
| 31 | redrawing the screen, thus can be much faster, after the initial cost of |
| 32 | attaching the text properties. |
| 33 | |
| 34 | Text properties can also be used for other purposes to identify text. For |
| 35 | example, add a text property on a function name, so that a search can be |
| 36 | defined to jump to the next/previous function. |
| 37 | |
| 38 | A text property is attached at a specific line and column, and has a specified |
| 39 | length. The property can span multiple lines. |
| 40 | |
| 41 | A text property has these fields: |
| 42 | "id" a number to be used as desired |
| 43 | "type" the name of a property type |
| 44 | |
| 45 | |
| 46 | Property Types ~ |
| 47 | *E971* |
Bram Moolenaar | 664f3cf | 2019-12-07 16:03:51 +0100 | [diff] [blame] | 48 | A text property normally has the name of a property type, which defines |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 49 | how to highlight the text. The property type can have these entries: |
| 50 | "highlight" name of the highlight group to use |
Bram Moolenaar | 574ee7b | 2019-11-13 23:04:29 +0100 | [diff] [blame] | 51 | "combine" when omitted or TRUE the text property highlighting is |
| 52 | combined with any syntax highlighting; when FALSE the |
Bram Moolenaar | de24a87 | 2019-05-05 15:48:00 +0200 | [diff] [blame] | 53 | text property highlighting replaces the syntax |
| 54 | highlighting |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 55 | "priority" when properties overlap, the one with the highest |
| 56 | priority will be used. |
| 57 | "start_incl" when TRUE inserts at the start position will be |
| 58 | included in the text property |
| 59 | "end_incl" when TRUE inserts at the end position will be |
| 60 | included in the text property |
| 61 | |
| 62 | |
| 63 | Example ~ |
| 64 | |
| 65 | Suppose line 11 in a buffer has this text (excluding the indent): |
| 66 | |
| 67 | The number 123 is smaller than 4567. |
| 68 | |
Bram Moolenaar | 4c05fa0 | 2019-01-01 15:32:17 +0100 | [diff] [blame] | 69 | To highlight the numbers in this text: > |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 70 | call prop_type_add('number', {'highlight': 'Constant'}) |
Bram Moolenaar | 9d87a37 | 2018-12-18 21:41:50 +0100 | [diff] [blame] | 71 | call prop_add(11, 12, {'length': 3, 'type': 'number'}) |
| 72 | call prop_add(11, 32, {'length': 4, 'type': 'number'}) |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 73 | |
Bram Moolenaar | 4c05fa0 | 2019-01-01 15:32:17 +0100 | [diff] [blame] | 74 | Try inserting or deleting lines above the text, you will see that the text |
| 75 | properties stick to the text, thus the line number is adjusted as needed. |
| 76 | |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 77 | Setting "start_incl" and "end_incl" is useful when white space surrounds the |
| 78 | text, e.g. for a function name. Using false is useful when the text starts |
| 79 | and/or ends with a specific character, such as the quote surrounding a string. |
| 80 | |
| 81 | func FuncName(arg) ~ |
| 82 | ^^^^^^^^ property with start_incl and end_incl set |
| 83 | |
| 84 | var = "text"; ~ |
| 85 | ^^^^^^ property with start_incl and end_incl not set |
| 86 | |
| 87 | Nevertheless, when text is inserted or deleted the text may need to be parsed |
Bram Moolenaar | 9d87a37 | 2018-12-18 21:41:50 +0100 | [diff] [blame] | 88 | and the text properties updated. But this can be done asynchronously. |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 89 | |
Bram Moolenaar | 96f45c0 | 2019-10-26 19:53:45 +0200 | [diff] [blame] | 90 | |
| 91 | Internal error *E967* |
| 92 | |
| 93 | If you see E967, please report the bug. You can do this at Github: |
| 94 | https://github.com/vim/vim/issues/new |
| 95 | |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 96 | ============================================================================== |
| 97 | 2. Functions *text-prop-functions* |
| 98 | |
| 99 | Manipulating text property types: |
| 100 | |
| 101 | prop_type_add({name}, {props}) define a new property type |
| 102 | prop_type_change({name}, {props}) change an existing property type |
| 103 | prop_type_delete({name} [, {props}]) delete a property type |
Bram Moolenaar | cb80aa2 | 2020-10-26 21:12:46 +0100 | [diff] [blame] | 104 | prop_type_get({name} [, {props}]) get property type values |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 105 | prop_type_list([{props}]) get list of property types |
| 106 | |
| 107 | |
| 108 | Manipulating text properties: |
| 109 | |
| 110 | prop_add({lnum}, {col}, {props}) add a text property |
Yegappan Lakshmanan | ccfb7c6 | 2021-08-16 21:39:09 +0200 | [diff] [blame] | 111 | prop_add_list({props}, [[{lnum}, {col}, {end-lnum}, {end-col}], ...]) |
| 112 | add a text property at multiple |
| 113 | positions. |
Bram Moolenaar | c8c8849 | 2018-12-27 23:59:26 +0100 | [diff] [blame] | 114 | prop_clear({lnum} [, {lnum-end} [, {bufnr}]]) |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 115 | remove all text properties |
| 116 | prop_find({props} [, {direction}]) search for a text property |
Bram Moolenaar | 7ceefb3 | 2020-05-01 16:07:38 +0200 | [diff] [blame] | 117 | prop_list({lnum} [, {props}]) text properties in {lnum} |
Bram Moolenaar | c8c8849 | 2018-12-27 23:59:26 +0100 | [diff] [blame] | 118 | prop_remove({props} [, {lnum} [, {lnum-end}]]) |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 119 | remove a text property |
| 120 | |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 121 | *prop_add()* *E965* |
| 122 | prop_add({lnum}, {col}, {props}) |
| 123 | Attach a text property at position {lnum}, {col}. {col} is |
| 124 | counted in bytes, use one for the first column. |
| 125 | If {lnum} is invalid an error is given. *E966* |
| 126 | If {col} is invalid an error is given. *E964* |
| 127 | |
| 128 | {props} is a dictionary with these fields: |
| 129 | length length of text in bytes, can only be used |
| 130 | for a property that does not continue in |
| 131 | another line; can be zero |
Bram Moolenaar | d2ea7cf | 2021-05-30 20:54:13 +0200 | [diff] [blame] | 132 | end_lnum line number for the end of text (inclusive) |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 133 | end_col column just after the text; not used when |
| 134 | "length" is present; when {col} and "end_col" |
| 135 | are equal, and "end_lnum" is omitted or equal |
| 136 | to {lnum}, this is a zero-width text property |
| 137 | bufnr buffer to add the property to; when omitted |
| 138 | the current buffer is used |
Bram Moolenaar | b17893a | 2020-03-14 08:19:51 +0100 | [diff] [blame] | 139 | id user defined ID for the property; must be a |
| 140 | number; when omitted zero is used |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 141 | type name of the text property type |
| 142 | All fields except "type" are optional. |
| 143 | |
| 144 | It is an error when both "length" and "end_lnum" or "end_col" |
| 145 | are given. Either use "length" or "end_col" for a property |
| 146 | within one line, or use "end_lnum" and "end_col" for a |
| 147 | property that spans more than one line. |
| 148 | When neither "length" nor "end_col" are given the property |
Bram Moolenaar | bc93ceb | 2020-02-26 13:36:21 +0100 | [diff] [blame] | 149 | will be zero-width. That means it will move with the text, as |
| 150 | a kind of mark. One character will be highlighted, if the |
| 151 | type specifies highlighting. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 152 | The property can end exactly at the last character of the |
| 153 | text, or just after it. In the last case, if text is appended |
| 154 | to the line, the text property size will increase, also when |
| 155 | the property type does not have "end_incl" set. |
| 156 | |
| 157 | "type" will first be looked up in the buffer the property is |
| 158 | added to. When not found, the global property types are used. |
| 159 | If not found an error is given. |
| 160 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 161 | Can also be used as a |method|: > |
| 162 | GetLnum()->prop_add(col, props) |
Yegappan Lakshmanan | 820d552 | 2021-09-17 21:07:35 +0200 | [diff] [blame] | 163 | < |
Yegappan Lakshmanan | ccfb7c6 | 2021-08-16 21:39:09 +0200 | [diff] [blame] | 164 | *prop_add_list()* |
| 165 | prop_add_list({props}, [[{lnum}, {col}, {end-lnum}, {end-col}], ...]) |
| 166 | Similar to prop_add(), but attaches a text property at |
| 167 | multiple positions in a buffer. |
| 168 | |
| 169 | {props} is a dictionary with these fields: |
| 170 | bufnr buffer to add the property to; when omitted |
| 171 | the current buffer is used |
| 172 | id user defined ID for the property; must be a |
| 173 | number; when omitted zero is used |
| 174 | type name of the text property type |
| 175 | All fields except "type" are optional. |
| 176 | |
| 177 | The second argument is a List of Lists where each list |
| 178 | specifies the starting and ending position of the text. The |
| 179 | first two items {lnum} and {col} specify the starting position |
| 180 | of the text where the property will be attached and the last |
| 181 | two items {end-lnum} and {end-col} specify the position just |
| 182 | after the text. |
| 183 | |
| 184 | Example: |
| 185 | call prop_add_list(#{type: 'MyProp', id: 2}, |
| 186 | \ [[1, 4, 1, 7], |
| 187 | \ [1, 15, 1, 20], |
| 188 | \ [2, 30, 3, 30]] |
| 189 | |
| 190 | Can also be used as a |method|: > |
| 191 | GetProp()->prop_add_list([[1, 1, 1, 2], [1, 4, 1, 8]]) |
| 192 | |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 193 | |
| 194 | prop_clear({lnum} [, {lnum-end} [, {props}]]) *prop_clear()* |
| 195 | Remove all text properties from line {lnum}. |
| 196 | When {lnum-end} is given, remove all text properties from line |
| 197 | {lnum} to {lnum-end} (inclusive). |
| 198 | |
| 199 | When {props} contains a "bufnr" item use this buffer, |
| 200 | otherwise use the current buffer. |
| 201 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 202 | Can also be used as a |method|: > |
| 203 | GetLnum()->prop_clear() |
| 204 | < |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 205 | *prop_find()* |
| 206 | prop_find({props} [, {direction}]) |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 207 | Search for a text property as specified with {props}: |
| 208 | id property with this ID |
| 209 | type property with this type name |
Bram Moolenaar | 24f21fd | 2021-03-27 22:07:29 +0100 | [diff] [blame] | 210 | both "id" and "type" must both match |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 211 | bufnr buffer to search in; when present a |
| 212 | start position with "lnum" and "col" |
| 213 | must be given; when omitted the |
| 214 | current buffer is used |
| 215 | lnum start in this line (when omitted start |
| 216 | at the cursor) |
| 217 | col start at this column (when omitted |
| 218 | and "lnum" is given: use column 1, |
| 219 | otherwise start at the cursor) |
| 220 | skipstart do not look for a match at the start |
| 221 | position |
| 222 | |
Bram Moolenaar | 24f21fd | 2021-03-27 22:07:29 +0100 | [diff] [blame] | 223 | A property matches when either "id" or "type" matches. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 224 | {direction} can be "f" for forward and "b" for backward. When |
| 225 | omitted forward search is performed. |
| 226 | |
| 227 | If a match is found then a Dict is returned with the entries |
| 228 | as with prop_list(), and additionally an "lnum" entry. |
| 229 | If no match is found then an empty Dict is returned. |
| 230 | |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 231 | |
| 232 | prop_list({lnum} [, {props}]) *prop_list()* |
Yegappan Lakshmanan | e021662 | 2021-11-23 11:46:32 +0000 | [diff] [blame] | 233 | Returns a List with all the text properties in line {lnum}. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 234 | |
Yegappan Lakshmanan | e021662 | 2021-11-23 11:46:32 +0000 | [diff] [blame] | 235 | The following optional items are supported in {props}: |
| 236 | bufnr use this buffer instead of the current buffer |
| 237 | end_lnum return text properties in all the lines |
| 238 | between {lnum} and {end_lnum} (inclusive). |
| 239 | A negative value is used as an offset from the |
| 240 | last buffer line; -1 refers to the last buffer |
| 241 | line. |
| 242 | types List of property type names. Return only text |
| 243 | properties that match one of the type names. |
| 244 | ids List of property identifiers. Return only text |
| 245 | properties with one of these identifiers. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 246 | |
| 247 | The properties are ordered by starting column and priority. |
| 248 | Each property is a Dict with these entries: |
Yegappan Lakshmanan | e021662 | 2021-11-23 11:46:32 +0000 | [diff] [blame] | 249 | lnum starting line number. Present only when |
| 250 | returning text properties between {lnum} and |
| 251 | {end_lnum}. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 252 | col starting column |
| 253 | length length in bytes, one more if line break is |
| 254 | included |
| 255 | id property ID |
| 256 | type name of the property type, omitted if |
| 257 | the type was deleted |
Martin Tournoij | e2390c7 | 2021-07-28 13:30:16 +0200 | [diff] [blame] | 258 | type_bufnr buffer number for which this type was defined; |
| 259 | 0 if the type is global |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 260 | start when TRUE property starts in this line |
| 261 | end when TRUE property ends in this line |
| 262 | |
| 263 | When "start" is zero the property started in a previous line, |
| 264 | the current one is a continuation. |
| 265 | When "end" is zero the property continues in the next line. |
| 266 | The line break after this line is included. |
| 267 | |
Yegappan Lakshmanan | e021662 | 2021-11-23 11:46:32 +0000 | [diff] [blame] | 268 | Returns an empty list on error. |
| 269 | |
| 270 | Examples: |
| 271 | " get text properties placed in line 5 |
| 272 | echo prop_list(5) |
| 273 | " get text properties placed in line 20 in buffer 4 |
| 274 | echo prop_list(20, {'bufnr': 4}) |
| 275 | " get all the text properties between line 1 and 20 |
| 276 | echo prop_list(1, {'end_lnum': 20}) |
| 277 | " get all the text properties of type 'myprop' |
| 278 | echo prop_list(1, {'types': ['myprop'], |
| 279 | \ 'end_lnum': -1}) |
| 280 | " get all the text properties of type 'prop1' or 'prop2' |
| 281 | echo prop_list(1, {'types': ['prop1', 'prop2'], |
| 282 | \ 'end_lnum': -1}) |
| 283 | " get all the text properties with ID 8 |
| 284 | echo prop_list(1, {'ids': [8], 'end_lnum': line('$')}) |
| 285 | " get all the text properties with ID 10 and 20 |
| 286 | echo prop_list(1, {'ids': [10, 20], 'end_lnum': -1}) |
| 287 | " get text properties with type 'myprop' and ID 100 |
| 288 | " in buffer 4. |
| 289 | echo prop_list(1, {'bufnr': 4, 'types': ['myprop'], |
| 290 | \ 'ids': [100], 'end_lnum': -1}) |
| 291 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 292 | Can also be used as a |method|: > |
| 293 | GetLnum()->prop_list() |
| 294 | < |
Bram Moolenaar | 7ff7846 | 2020-07-10 22:00:53 +0200 | [diff] [blame] | 295 | *prop_remove()* *E968* *E860* |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 296 | prop_remove({props} [, {lnum} [, {lnum-end}]]) |
| 297 | Remove a matching text property from line {lnum}. When |
| 298 | {lnum-end} is given, remove matching text properties from line |
| 299 | {lnum} to {lnum-end} (inclusive). |
| 300 | When {lnum} is omitted remove matching text properties from |
Bram Moolenaar | d2ea7cf | 2021-05-30 20:54:13 +0200 | [diff] [blame] | 301 | all lines (this requires going over all lines, thus will be a |
| 302 | bit slow for a buffer with many lines). |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 303 | |
| 304 | {props} is a dictionary with these fields: |
| 305 | id remove text properties with this ID |
| 306 | type remove text properties with this type name |
Bram Moolenaar | 49b79bd | 2020-03-05 21:52:55 +0100 | [diff] [blame] | 307 | both "id" and "type" must both match |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 308 | bufnr use this buffer instead of the current one |
| 309 | all when TRUE remove all matching text properties, |
| 310 | not just the first one |
| 311 | A property matches when either "id" or "type" matches. |
| 312 | If buffer "bufnr" does not exist you get an error message. |
| 313 | If buffer "bufnr" is not loaded then nothing happens. |
| 314 | |
| 315 | Returns the number of properties that were removed. |
| 316 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 317 | Can also be used as a |method|: > |
| 318 | GetProps()->prop_remove() |
| 319 | |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 320 | |
| 321 | prop_type_add({name}, {props}) *prop_type_add()* *E969* *E970* |
| 322 | Add a text property type {name}. If a property type with this |
Bram Moolenaar | 06fe74a | 2019-08-31 16:20:32 +0200 | [diff] [blame] | 323 | name already exists an error is given. Nothing is returned. |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 324 | {props} is a dictionary with these optional fields: |
| 325 | bufnr define the property only for this buffer; this |
| 326 | avoids name collisions and automatically |
| 327 | clears the property types when the buffer is |
| 328 | deleted. |
| 329 | highlight name of highlight group to use |
| 330 | priority when a character has multiple text |
| 331 | properties the one with the highest priority |
| 332 | will be used; negative values can be used, the |
| 333 | default priority is zero |
Bram Moolenaar | dad4473 | 2021-03-31 20:07:33 +0200 | [diff] [blame] | 334 | combine when omitted or TRUE combine the highlight |
| 335 | with any syntax highlight; when FALSE syntax |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 336 | highlight will not be used |
| 337 | start_incl when TRUE inserts at the start position will |
| 338 | be included in the text property |
| 339 | end_incl when TRUE inserts at the end position will be |
| 340 | included in the text property |
| 341 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 342 | Can also be used as a |method|: > |
| 343 | GetPropName()->prop_type_add(props) |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 344 | |
| 345 | prop_type_change({name}, {props}) *prop_type_change()* |
| 346 | Change properties of an existing text property type. If a |
| 347 | property with this name does not exist an error is given. |
| 348 | The {props} argument is just like |prop_type_add()|. |
| 349 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 350 | Can also be used as a |method|: > |
| 351 | GetPropName()->prop_type_change(props) |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 352 | |
| 353 | prop_type_delete({name} [, {props}]) *prop_type_delete()* |
| 354 | Remove the text property type {name}. When text properties |
| 355 | using the type {name} are still in place, they will not have |
| 356 | an effect and can no longer be removed by name. |
| 357 | |
| 358 | {props} can contain a "bufnr" item. When it is given, delete |
| 359 | a property type from this buffer instead of from the global |
| 360 | property types. |
| 361 | |
| 362 | When text property type {name} is not found there is no error. |
| 363 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 364 | Can also be used as a |method|: > |
| 365 | GetPropName()->prop_type_delete() |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 366 | |
Bram Moolenaar | cb80aa2 | 2020-10-26 21:12:46 +0100 | [diff] [blame] | 367 | prop_type_get({name} [, {props}]) *prop_type_get()* |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 368 | Returns the properties of property type {name}. This is a |
| 369 | dictionary with the same fields as was given to |
| 370 | prop_type_add(). |
| 371 | When the property type {name} does not exist, an empty |
| 372 | dictionary is returned. |
| 373 | |
| 374 | {props} can contain a "bufnr" item. When it is given, use |
| 375 | this buffer instead of the global property types. |
| 376 | |
Bram Moolenaar | a5a7882 | 2019-09-04 21:57:18 +0200 | [diff] [blame] | 377 | Can also be used as a |method|: > |
| 378 | GetPropName()->prop_type_get() |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 379 | |
| 380 | prop_type_list([{props}]) *prop_type_list()* |
| 381 | Returns a list with all property type names. |
| 382 | |
| 383 | {props} can contain a "bufnr" item. When it is given, use |
| 384 | this buffer instead of the global property types. |
| 385 | |
Bram Moolenaar | ed997ad | 2019-07-21 16:42:00 +0200 | [diff] [blame] | 386 | |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 387 | ============================================================================== |
| 388 | 3. When text changes *text-prop-changes* |
| 389 | |
| 390 | Vim will do its best to keep the text properties on the text where it was |
| 391 | attached. When inserting or deleting text the properties after the change |
| 392 | will move accordingly. |
| 393 | |
| 394 | When text is deleted and a text property no longer includes any text, it is |
| 395 | deleted. However, a text property that was defined as zero-width will remain, |
| 396 | unless the whole line is deleted. |
Bram Moolenaar | 30e9b3c | 2019-09-07 16:24:12 +0200 | [diff] [blame] | 397 | *E275* |
Bram Moolenaar | 45311b5 | 2019-08-13 22:27:32 +0200 | [diff] [blame] | 398 | When a buffer is unloaded, all the text properties are gone. There is no way |
| 399 | to store the properties in a file. You can only re-create them. When a |
| 400 | buffer is hidden the text is preserved and so are the text properties. It is |
| 401 | not possible to add text properties to an unloaded buffer. |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 402 | |
| 403 | When using replace mode, the text properties stay on the same character |
| 404 | positions, even though the characters themselves change. |
| 405 | |
Bram Moolenaar | 68e6560 | 2019-05-26 21:33:31 +0200 | [diff] [blame] | 406 | To update text properties after the text was changed, install a callback with |
| 407 | `listener_add()`. E.g, if your plugin does spell checking, you can have the |
| 408 | callback update spelling mistakes in the changed text. Vim will move the |
| 409 | properties below the changed text, so that they still highlight the same text, |
| 410 | thus you don't need to update these. |
| 411 | |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 412 | |
Bram Moolenaar | bc93ceb | 2020-02-26 13:36:21 +0100 | [diff] [blame] | 413 | Text property columns are not updated or copied: ~ |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 414 | |
| 415 | - When setting the line with |setline()| or through an interface, such as Lua, |
Bram Moolenaar | a6c27c4 | 2019-05-09 19:16:22 +0200 | [diff] [blame] | 416 | Tcl or Python. Vim does not know what text got inserted or deleted. |
Bram Moolenaar | bc93ceb | 2020-02-26 13:36:21 +0100 | [diff] [blame] | 417 | - With a command like `:move`, which takes a line of text out of context. |
Bram Moolenaar | d09091d | 2019-01-17 16:07:22 +0100 | [diff] [blame] | 418 | |
Bram Moolenaar | 98aefe7 | 2018-12-13 22:20:09 +0100 | [diff] [blame] | 419 | |
| 420 | vim:tw=78:ts=8:noet:ft=help:norl: |