Lines Matching full:be
4 The message "A percent sign appearing in text is a literal" can be caused by code like:
10 This code should be replaced with code like:
16 This can be a bit surprising and could be a field that was not
23 The message "Unknown long name for role/modifier" can be caused by code like:
29 This code should be replaced with code like:
42 The message "Last character before field definition is a field type" can be caused by code like:
49 This code should be replaced with code like:
61 The message "Encoding format uses different number of arguments" can be caused by code like:
67 This code should be replaced with code like:
76 'Only one field role can be used'
79 The message "Only one field role can be used" can be caused by code like:
85 This code should be replaced with code like:
94 The message "Potential missing slash after C, D, N, L, or T with format" can be caused by code like:
100 This code should be replaced with code like:
106 The "%6.6s" will be a literal, not a field format. While
110 'An encoding format cannot be given (roles: DNLT)'
113 The message "An encoding format cannot be given (roles: DNLT)" can be caused by code like:
124 'Format cannot be given when content is present (roles: CDLN)'
127 The message "Format cannot be given when content is present (roles: CDLN)" can be caused by code li…
137 in it, like "{N:Type of I/O}"; backslashes should be escaped,
145 The message "Field has color without fg- or bg- (role: C)" can be caused by code like:
151 This code should be replaced with code like:
157 Colors must be prefixed by either "fg-" or "bg-".
163 The message "Field has invalid color or effect (role: C)" can be caused by code like:
169 This code should be replaced with code like:
178 be prefixed by either "fg-" or "bg-". Effects are
181 be separated by commas.
187 The message "Field has humanize modifier but no format string" can be caused by code like:
193 This code should be replaced with code like:
206 The message "Field has hn-* modifier but not 'h' modifier" can be caused by code like:
212 This code should be replaced with code like:
225 The message "Value field must have a name (as content)")" can be caused by code like:
231 This code should be replaced with code like:
245 The message "Use hyphens, not underscores, for value field name" can be caused by code like:
251 This code should be replaced with code like:
258 flag can be used to generate underscores in JSON, if desired.
265 The message "Value field name cannot start with digit" can be caused by code like:
271 This code should be replaced with code like:
280 'Value field name should be lower case'
283 The message "Value field name should be lower case" can be caused by code like:
289 This code should be replaced with code like:
295 Lower case is more civilized. Even TLAs should be lower case
300 'Value field name should be longer than two characters'
303 The message "Value field name should be longer than two characters" can be caused by code like:
309 This code should be replaced with code like:
315 Field names should be descriptive, and it's hard to
316 be descriptive in less than two characters. Consider
326 The message "Value field name contains invalid character" can be caused by code like:
332 This code should be replaced with code like:
346 The message "decoration field contains invalid character" can be caused by code like:
352 This code should be replaced with code like:
364 'Anchor content should be decimal width'
367 The message "Anchor content should be decimal width" can be caused by code like:
373 This code should be replaced with code like:
380 the set of anchored fields. The value can be positive
386 'Anchor format should be "%d"'
389 The message "Anchor format should be "%d"" can be caused by code like:
395 This code should be replaced with code like:
402 if must be in an 'int' argument, represented by the "%d" format.
409 The message "Anchor cannot have both format and encoding format")" can be caused by code like:
415 This code should be replaced with code like:
428 The message "Max width only valid for strings" can be caused by code like:
434 This code should be replaced with code like:
444 like "{:tag/%6..6d}" where only one period should be used.