On Fri, Mar 11, 2011 at 1:23 PM, Rob wrote:
> I have noticed that 'nowrap' gets set in the (clewn)_console. I
> usually work with 2 windows and a vertical split so find 'wrap' more
> useful (eg. for back traces). Is there a reason why this is done?
>
> 'autocmd BufWinEnter' in debugger.py appears to set nowrap for all
> clewn buffers, perhaps it is more important for (clewn)_dbgvar and
> others?
>
The 'nowrap' setting avoids the display in (clewn)_console of the
multiple physical lines of a single very long logical line output by
gdb. This occurs for example when printing a string in a large
allocated memory (unless gdb is set with 'set print null-stop' which
is not the default). In these cases, browsing the 12 lines of the
(clewn)_console becomes clumsy.
To illustrate this, debug the following program and ':Cprint str' at
the 'return 0;' statement in a 70 characters wide terminal, then
browse the (clewn)_console with 'wrap' on:
#include <string.h>
#define ARRAY_SIZE 1024
int main(int argc, char ** argv)
{
int i = ARRAY_SIZE;
char str[ARRAY_SIZE];
while (i--)
str[i] = (char) i;
strcpy(str, "foo");
return 0;
}
The 'nowrap' setting is not needed by the implementation of
(clewn)_dbgvar.
Do you think the 'wrap' setting should be configurable ?
--
Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
