PRs for manpage 'script(1)'
This is an experimental report containing PRs for manpage 'script(1)' as of Fri Dec 13 07:39:03 2013 UTC. See notes.
PRs for manpage 'script(1)':
|o||2011/10/12||bin/161526||script(1) outputs corrupt if input is not from a terminal|
|o||2010/11/12||bin/152154||script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)|
|o||2010/11/11||bin/152132||script(1): [patch] Useless code in script.c (part 2)|
|p||2007/07/09||bin/114465||brian||[patch] [request] script(1): add really cool -d, -p & -r options from NetBSD|
|o||2006/03/03||bin/94052||[patch] Adds option to script(1) to suppress carriage-returns in log file.|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.