nvi file status percentage is garbage

Bug #382282 reported by Dave Wolfe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvi (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvi

Control-G displays a file status message at the bottom of the terminal window, for example:

zz: unmodified: line 52 of 14253 [140733193388032%]

Note that the percentage location in the file is absurd.

I'm using a stock Ubuntu desktop 9.04 on a dual-processor AMD64. Nvi is version 1.81.6-5 installed with that version. This behavior first appeared when I upgraded from 8.04lts (to 8.10 then) to 9.04. I didn't use the 8.10 system long enough to notice if this problem existed in it.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: nvi 1.81.6-5
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvi
Uname: Linux 2.6.28-11-generic x86_64

Tags: nvi
Revision history for this message
Dave Wolfe (dave-wolfeworks) wrote :
Revision history for this message
lichray (lichray) wrote :

I'm maintaining a version of nvi. Can you provide me a file to reproduce this problem? Thanks.

Revision history for this message
Dave Wolfe (dave-wolfeworks) wrote : Re: [Bug 382282] Re: nvi file status percentage is garbage

Once I figured out how to "back-grade" and lock the nvi version I
haven't used the post-1.79 versions and don't have any of them installed
anywhere. I'll see if I can make some time to re-install a later version
tomorrow and try to find a file I can share that exhibits the problem.
Ditto for bug 382288 (nvi line numbering shows non-existant lines with
absurd numbers).

lichray wrote:
> I'm maintaining a version of nvi. Can you provide me a file to reproduce
> this problem? Thanks.
>

--

/*Dave Wolfe
Wolfe Works LLC*/

Revision history for this message
Dave Wolfe (dave-wolfeworks) wrote :

As I said, I don't have the same versions of either nvi, Ubuntu, or the original file, so I'm unable to reproduce this problem. Perhaps it's already been fixed in a subsequent build. Go ahead and close it as unconfirmed.

Revision history for this message
Tobias Heider (tobhe) wrote :

Closing because I can't reproduce it on 1.81.6-18. Feel free to comment or reopen if the issue persists and you have more info on how to reproduce it.

Changed in nvi (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.