From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Subject: Re: [9fans] xd bug From: "Russ Cox" Date: Mon, 14 Jul 2008 12:43:58 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20080714164232.2A0A51E8C6E@holo.morphisms.net> Topicbox-Message-UUID: e621bcbe-ead3-11e9-9d60-3106f5b1d025 > Hello. Regarding my previous question, the file /n/sources/contrib/ > pietro/xd.out shows a bug in xd regarding characters that can't be > printed with the %c format. There should be no space between a non- > printing and a printing character; but the two spaces screw the rest > of the line up. This shows a deficiency in the table-based > implementation. I'll do my best to fix it in a clean way. Thanks. It would help a lot if (1) you cut and pasted things into email instead of making us go look on sources for four-line files and (2) you told us exactly what you thought was wrong. Your xd.out says: % xd -c -x bad 0000000 e0 Q R S \n 0 e0515253 0a000000 0000005 which looks fine to me. If I create the same file and add some more text just to fill things out, I get: % xd -c -b -x a | sed 6q 0000000 e0 Q R S \n L o r e m i p s u m 0 e0 51 52 53 0a 4c 6f 72 65 6d 20 69 70 73 75 6d 0 e0515253 0a4c6f72 656d2069 7073756d 0000010 d o l o r s i t a m e t , 10 20 64 6f 6c 6f 72 20 73 69 74 20 61 6d 65 74 2c 10 20646f6c 6f722073 69742061 6d65742c which still looks just fine. In particular I don't see any alignment difference between the first line and the second line. Russ