| /freebsd-13.1/contrib/bc/gen/ |
| H A D | strgen.c | 209 int c, count, slashes, err = IO_ERR; in main() local
241 c = count = slashes = 0; in main()
244 while (slashes < 2 && (c = fgetc(in)) >= 0) { in main()
245 slashes += (slashes == 1 && c == '/' && fgetc(in) == '\n'); in main()
246 slashes += (!slashes && c == '/' && fgetc(in) == '*'); in main()
|
| /freebsd-13.1/contrib/llvm-project/llvm/lib/Support/Unix/ |
| H A D | Program.inc | 72 // Use the given path verbatim if it contains any slashes; this matches
|
| /freebsd-13.1/contrib/diff/doc/ |
| H A D | diff.texi | 2842 have enough slashes to satisfy the @option{-p@var{num}} or
2916 count tells @command{patch} how many slashes, along with the directory
2918 of one or more adjacent slashes is counted as a single slash. By
2928 @command{patch} looks for each file (after any slashes have been stripped)
3216 Also, traditional @command{patch} simply counted slashes when
3218 components. That is, a sequence of one or more adjacent slashes now
3246 the same number of slashes.
3317 slashes. The @option{-N} option lets the patch create and remove
3356 directories whose names do not have slashes. This reduces confusion
3359 file names have different numbers of slashes. For example, do not
[all …]
|
| /freebsd-13.1/contrib/opie/ |
| H A D | README | 329 slashes in them properly and can choke badly on the definition of the key
|
| /freebsd-13.1/usr.sbin/cron/doc/ |
| H A D | MAIL | 142 to start on and N with slashes). I took modulo the day of year as a
|
| /freebsd-13.1/contrib/kyua/ |
| H A D | NEWS.md | 285 variable where, for example, consecutive and trailing slashes have
|
| /freebsd-13.1/crypto/heimdal/doc/ |
| H A D | setup.texi | 70 separated by slashes (@samp{/}). The @samp{other-var} variable will thus
|
| /freebsd-13.1/crypto/heimdal/ |
| H A D | ltmain.sh | 4665 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/unbound/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/sqlite3/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/openpam/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/file/ |
| H A D | ltmain.sh | 6052 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/openbsm/config/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/ntp/sntp/libevent/build-aux/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/ldns/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/libevent/ |
| H A D | ltmain.sh | 6049 /* no slashes; search PATH */
|
| /freebsd-13.1/contrib/tcsh/ |
| H A D | Fixes | 209 55. Avoid double slashes in cdpath (Corinna Vinschen)
|
| /freebsd-13.1/contrib/xz/ |
| H A D | ChangeLog | 1431 Some paths use slashes instead of backslashes as directory
|
| /freebsd-13.1/contrib/unbound/doc/ |
| H A D | Changelog | 567 not hang. removed trailing slashes from configure paths. Moved iOS
|
| /freebsd-13.1/contrib/sendmail/ |
| H A D | RELEASE_NOTES | 8915 of leading slashes still goes to the *file* mailer. This
|
| /freebsd-13.1/sys/contrib/dev/acpica/ |
| H A D | changes.txt | 6298 backslashes in all pathnames to forward slashes, for readability. Include
|