HomeSort by: relevance | last modified time | path
    Searched refs:spaces (Results 1 - 25 of 50) sorted by relevancy

1 2

  /src/usr.bin/make/unit-tests/
opt-debug-errors.mk 8 all: fail-spaces
14 # XXX: The debug output folds the spaces, showing '3 spaces' instead of
15 # the correct '3 spaces'.
16 fail-spaces:
17 echo '3 spaces'; false
19 # XXX: The debug output folds the spaces, showing 'echo \ indented' instead
35 # of the lines, usually at column 73. All spaces before the continuation
37 # irrelevant. Having these spaces collapsed makes sense to show the command
opt-debug-errors.exp 1 echo '3 spaces'; false
2 3 spaces
4 *** Failed target: fail-spaces
5 *** Failed command: echo '3 spaces'; false
varmod-to-lower.mk 22 .if ${:Umultiple spaces:tl} != "multiple spaces"
opt-debug-errors-jobs.exp 1 echo '3 spaces'; false
2 3 spaces
4 *** Failed target: fail-spaces
7 echo '3 spaces'; false
8 *** [fail-spaces] Error code 1
varmod-to-title.mk 22 .if ${:Umultiple spaces:tt} != "Multiple Spaces"
26 # Note words only count if separated by spaces
opt-debug-errors-jobs.mk 8 all: fail-spaces
15 fail-spaces:
16 echo '3 spaces'; false
31 # of the lines, usually at column 73. All spaces before the continuation
escape.exp 45 VAR1BSNLss=:first line two spaces on second line:
48 VAR1BSNLxx=:first line many spaces and tabs [ ] on second line:
57 second line spaces should be retained':
59 second line spaces should be retained:
87 second line spaces should be retained':
89 second line spaces should be retained:
varmod-to-upper.mk 19 # not as a list of words. Therefore, the adjacent spaces are preserved.
cond-cmp-numeric.mk 44 # Leading spaces are allowed for numbers.
51 # Trailing spaces are NOT allowed for numbers.
varmod-exclam-shell.mk 25 # converted to spaces.
varmod-order-string.mk 14 # and the additional spaces between them are removed.
varname-make_print_var_on_error-jobs.mk 10 # contains spaces as well, this value is only intended as a first hint to what
directive-export-gmake.mk 26 # Contrary to the usual variable assignments, spaces are significant
29 export VAR= leading spaces
30 .if ${:!echo "\$VAR"!} != " leading spaces"
34 # Contrary to the usual variable assignments, spaces are significant
var-op-assign.mk 71 VAR(spaces in parentheses)= ()
72 VAR{spaces in braces}= {}
78 VARNAME_PAREN= VAR(spaces in parentheses)
79 VARNAME_BRACES= VAR{spaces in braces}
deptgt-makeflags.mk 32 .MAKEFLAGS: VAR="value"' with'\ spaces
33 .if ${VAR} != "value with spaces"
40 .if ${VAR} != "value with spaces"
parse-var.mk 79 # In variable assignments, there may be spaces in the middle of the left-hand
81 # Leading spaces (but not tabs) are possible but unusual.
82 # Trailing spaces are common in some coding styles, others omit them.
cond-func.mk 12 ${:UA B}= variable name with spaces
78 # There may be spaces around the operators and parentheses, and even
79 # inside the parentheses. The spaces inside the parentheses are not
escape.mk 175 two spaces on second line
181 many spaces and tabs [ ] on second line
202 second line spaces should be retained':
243 second line spaces should be retained':
opt-debug-jobs.mk 18 # Multiple spaces are preserved in the command, as they might be
varmod-head.mk 47 # the output "before after", with two spaces. Since 2020.07.20.14.50.41, the
cond-func-defined.mk 6 ${:UA B}= variable name with spaces
directive.mk 12 . indented 2 spaces
varmod-to-separator.mk 84 # spaces have been replaced with '/'. This single word does not start with
91 # word since all spaces have been replaced with x. Because of this single
99 # ':S' replaces the 2 'b's with spaces. These spaces are part of the word,
109 # newly added spaces are treated as word separators, resulting in 3 words.
  /src/sys/netinet/
accf_http.c 269 int i, cc, spaces, inspaces; local in function:soparsehttpvers
276 inspaces = spaces = 0;
285 spaces++;
294 if (spaces != 2) {
  /src/share/mk/
bsd.clean.mk 51 # or CLEANDIRFILES is not completely empty but contains spaces.
57 # CLEANFILES = "filename with spaces".

Completed in 28 milliseconds

1 2