I see that I didn't fix all the misuses of the term nice value
so I installed this further patch. I added a NEWS item.
2005-09-09 Paul Eggert [EMAIL PROTECTED]
* NEWS: Document niceness vs nice value.
* configure.ac (utils_cv_func_setpriority): Simplify the tests.
Where can i get the design documentation for core utils? i.e basic algorithm
for
the utilities. Sometimes it is difficult to know what a particular code
fragment
is doing by just looking at the code itself.
Unfortunately, you've stumbled across one of the weakness of open source.
Many
Paul Eggert [EMAIL PROTECTED] writes:
--- NEWS 29 Aug 2005 21:14:06 - 1.305
+++ NEWS 9 Sep 2005 19:57:59 -
@@ -103,6 +103,11 @@ GNU coreutils NEWS
--indicator-style=slash. Use --file-type or
--indicator-style=file-type to get -p's old
Andreas Schwab [EMAIL PROTECTED] writes:
+Documentation and diagnostics now refer to nicenesses (commonly
+in the range -20...19 rather than nice values (commonly 0...39).
Typo: a close paren is missing.
Thanks; I fixed that.
___
Greetings.
I'm reporting a bug with csplit coreutils 5.2.1, compiled from sources on a
SuSE 9.3 system. It seems this bug was previously reported over a year
ago (see
http://lists.gnu.org/archive/html/bug-coreutils/2004-08/msg00112.html)
but it was never squashed.
In short, csplit produces
