William Shipley Sun, 12 Dec 2010 17:57:17 -0800
This bug is fixed in nano 2.2.4-1, so I recommend that, if you haven't already, upgrade to the latest version.
