9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] xd bug
Date: Mon, 14 Jul 2008 12:43:58 -0400	[thread overview]
Message-ID: <20080714164232.2A0A51E8C6E@holo.morphisms.net> (raw)
In-Reply-To: <DEA2A36D-F837-41A4-8553-97093BFDC218@mac.com>

> 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



  reply	other threads:[~2008-07-14 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 21:26 Pietro Gagliardi
2008-07-14 16:43 ` Russ Cox [this message]
2008-07-14 17:02   ` Pietro Gagliardi
2008-07-14 17:13     ` erik quanstrom
2008-07-14 21:10       ` Pietro Gagliardi
2008-07-14 17:22     ` Russ Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080714164232.2A0A51E8C6E@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).