Bug 55971 - Word-wrap broken in 2.9.6-2
Word-wrap broken in 2.9.6-2
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: joe (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-11-09 12:02 EST by Alex Butcher
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-11-09 12:03:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alex Butcher 2001-11-09 12:02:57 EST
Description of Problem:

Word-wrap appears to be broken in this version; if you type something like:

dfg dfsg sdfg sdfg sdfg sdfg dsfg g g g g g g g g g g g g g g g g g g g g g g g

[keep typing 'g <space>']

joe appears to ignore the spaces between the g's and splits the line far
too early. I've downgraded to 2.8-43 (from rawhide some time ago, I think)
which doesn't exhibit this problem.
How Reproducible:

Version-Release number of selected component (if applicable):

2.9.6-2

Steps to Reproduce:

1.type something like:

dfg dfsg sdfg sdfg sdfg sdfg dsfg g g g g g g g g g g g g g g g g g g g g g g g

[keep typing 'g <space>']

2.Observe strange line split

3.Sulk

Actual Results:

dfg dfsg sdfg sdfg sdfg sdfg <CR>
dsfg g g g g g g g g g g g g g g g g g g g g g g 

Expected Results:

dfg dfsg sdfg sdfg sdfg sdfg dsfg g g g g g g g g g g g g g g g g g g g g g
<CR> 
g g

Additional Information:

Default config from RH7.2.

Reproducibility appears to depend on how many longer 'words' there are at
the beginning of the line. Most curious. The strings above have been tested
and demonstrate the problem though. Just paste 'em in. :)
Comment 1 Trond Eivind Glomsrxd 2001-11-09 12:21:14 EST
Fixed in joe-2.9.7-1

Note You need to log in before you can comment on or make changes to this bug.