Searched refs:traditional (Results 1 – 3 of 3) sorted by relevance
198 static bool traditional; variable1709 traditional = true; in main()1807 if (!modern || traditional) in main()1815 if ((traditional || argv[optind][0] == '+') in main()1825 if ((traditional || argv[optind + 1][0] == '+' in main()1829 if (traditional && parse_old_offset (argv[optind], &o1)) in main()1848 if (traditional in main()1862 if (traditional && 1 < n_files) in main()
120 * sum: (coreutils)sum invocation. Print traditional checksum.1590 containing traditional usage like @samp{sort +1} or @samp{tail +10},1979 od [@var{option}]@dots{} --traditional [@var{file}]@c2207 @item --traditional2208 @opindex --traditional2209 Recognize the non-option label argument that traditional @command{od}2213 od --traditional [@var{file}] [[+]@var{offset}[.][b] [[+]@var{label}[.][b]]]3270 can be replaced by @samp{+} in the traditional option syntax with the3272 1003.1-2001 traditional usage overrides normal usage when the two3277 Scripts intended for use on standard hosts should avoid traditional[all …]
1286 sort, tail, and uniq now support traditional usage like 'sort +2'2795 ls -l now uses the traditional three field time style rather than4953 the traditional "Jun 21 13:09".5054 even without --traditional. This is a change in behavior if there5115 'chown user.group file' now has its traditional meaning even when5593 use traditional timestamp format when in the POSIX locale.5613 traditional (and rarely desirable) cp -r behavior.5698 - The 'posix-iso' time style gives traditional POSIX-locale