PRs for manpage 'vi(1)'
This is an experimental report containing PRs for manpage 'vi(1)' as of Fri May 30 07:39:56 2014 UTC. See notes.
PRs for manpage 'vi(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/09/28 | bin/182463 | vi(1): vi core dumps on exit with a specific vi.exrc [regression] | |
| o | 2004/07/15 | bin/69083 | [patch] vi(1) basic modelines for contrib/nvi | |
| o | 2003/10/20 | bin/58293 | vi(1) replace with CR (ASCII 13) doesn't work | |
| a | 2000/12/28 | bin/23912 | vi(1) underflow of cnt in vs_paint() by O_NUMBER_LENGTH when both leftright and number options in use | |
| o | 2000/10/21 | bin/22182 | vi(1) options noprint/print/octal broken | |
| o | 1999/08/26 | bin/13397 | vi(1) nvi mishandles tags files under certain conditions. |
Notes
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.