Developer Cheatsheet formatting...

[Mike Hearn]

On Mon, 15 Nov 2004 08:37:18 -0800, Duane Clark wrote:
> Yes, I frankly think that is a bug in Mozilla/Firefox, but it has been 
> that way for a very long time. The width in the case of the above link 
> is being caused by the string in the +relay section beginning:
>    RtlEnterCriticalSection;RtlLeaveCriticalSection;...
> To make it display at a more reasonable width, the string needs to be 
> shortened or split up.

It's not a Gecko bug, I'm pretty sure of that, it's just me sucking.

The real fix is for everybody to by flat screens and use 1280x1024 screen
resolutions, but a quick hack would be to insert some spaces into that
string so line breaks can be inserted. I think the following patch should
help.

Index: developer-cheatsheet.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/developer-cheatsheet.template,v
retrieving revision 1.1
diff -u -p -r1.1 developer-cheatsheet.template
--- developer-cheatsheet.template	10 Nov 2004 00:20:10 -0000	1.1
+++ developer-cheatsheet.template	15 Nov 2004 17:04:06 -0000
@@ -75,7 +75,7 @@
         in the [Debug] section if you're being overwhelmed by certain
         functions. A good initial value for RelayExclude is:<p>
 
-          <code cols="72"> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel;_LeaveSysLevel;_CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap;LOCAL_Lock;LOCAL_Unlock </code><p>
+          <code cols="72"> RtlEnterCriticalSection;RtlLeaveCriticalSection;_EnterSysLevel; _LeaveSysLevel;_CheckNotSysLevel;RtlAllocateHeap;RtlFreeHeap; LOCAL_Lock;LOCAL_Unlock </code><p>
 
         Most of these functions are called a lot, but don't usually
         give any clues as to why a program might be failing. <p>