Subject: bug#215: view-lossage should go to point-max

From: "Drew Adams" <[email-masked]>
Date: Wed, 22 Feb 2012 08:37:09 -0800

> Version: 23.1
> It has done since 23.1.

No.  That does _not_ answer the bug report, which also stated that hard-coding
100 as the number of keys printed is not right.  You are trivializing the bug.

>From the OP and followup thread:

>>> Also how quaint hardwiring 100...
>>
>> I would very much like to see that 100 be increased a great
>> deal (e.g. 1000), and preferably made an option. This has been
>> requested before, but nothing has come of it.

Please increase the default value of this limit and make it a user option - or
at least a defvar.