|
|
9.
|
|
|
B<annotate-output> will execute the specified program, while prepending every line with the current time and O for stdout and E for stderr.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:10
|
|
|
16.
|
|
|
$ annotate-output make 
21:41:21 I: Started make
21:41:21 O: gcc -Wall program.c
21:43:18 E: program.c: Couldn't compile, and took me ages to find out
21:43:19 E: collect2: ld returned 1 exit status
21:43:19 E: make: *** [all] Error 1
21:43:19 I: Finished with exitcode 2
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:30
|
|
|
18.
|
|
|
Since stdout and stderr are processed in parallel, it can happen that some lines received on stdout will show up before later-printed stderr lines (and vice-versa).
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:36
|
|
|
19.
|
|
|
This is unfortunately very hard to fix with the current annotation strategy. A fix would involve switching to PTRACE'ing the process. Giving nice a (much) higher priority over the executed program could however cause this behaviour to show up less frequently.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:41
|
|
|
20.
|
|
|
The program does not work as well when the output is not linewise. In particular, when an interactive program asks for input, the question might not be shown until after you have answered it. This will give the impression that the annotated program has hung, while it has not.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:46
|
|
|
24.
|
|
|
This program is community-supported (meaning: you'll need to fix it yourself). Patches are however appreciated, as is any feedback (positive or negative).
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:54
|
|
|
26.
|
|
|
B<annotate-output> was written by Jeroen van Wolffelaar E<lt>jeroen@wolffelaar.nlE<gt> This manpage comes under the same copyright as annotate-output itself, read /usr/bin/annotate-output (or wherever you install it) for the details.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/annotate-output.1:59
|
|
|
28.
|
|
|
archpath - output arch (tla/Bazaar) archive names, with support for branches
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:4
|
|
|
32.
|
|
|
B<archpath> is intended to be run in an arch (tla or Bazaar) working copy.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:15
|
|
|
33.
|
|
|
In its simplest usage, B<archpath> with no parameters outputs the package name (archive/category--branch--version) associated with the working copy.
|
|
|
type: Plain text
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:20
|
