Bernd Jendrissek <> writes:

> On Tue, Aug 14, 2012 at 10:18 AM, Thomas Rast <> wrote:
>> Can you try the following:
>>   git ls-files --debug 
>> gnetlist/tests/common/outputs/osmond/
>>   cp .git/index .git/index.orig
>>   touch gnetlist/tests/common/outputs/osmond/
>>   # note, it is important that you run diff first
>>   git diff gnetlist/tests/common/outputs/osmond/
>>   git diff-files -p 
>> gnetlist/tests/common/outputs/osmond/
>>   git ls-files --debug 
>> gnetlist/tests/common/outputs/osmond/
> I'm can't tell what this was supposed to prove, but I think it's
> proven that I'm in the wrong mailing list, and that I should be taking
> this up with gnome-terminal. The Q1 part deletion line seems to be
> appearing (in the terminal) only after I've copy&pasted it into
> another terminal.
> Running the same commands in xterm (correctly) shows the Q1 part
> deletion line without having to copy & paste.

Fun stuff.  This will be very interesting to debug.  It's still
possible, though perhaps not extremely likely, that git is writing
garbage to the terminal and it just happens to work for xterm.

Whatever you do next, *please* post the *exact* file contents *and*
output in a format that does not suffer any transport damage, neither to
whitespace nor to binary data (such as terminal escapes).  Piping
through xxd comes to mind, perhaps by using

  GIT_PAGER=xxd git -p diff ....  >diff-hexdump

etc. to ensure that git takes the same code paths as when writing to

Cut&paste from a terminal will at best give you exactly what the
terminal figures it is *currently displaying*, which is completely
different from what programs write to it.  At worst, it will also suffer
whitespace damage.  So pretty much everything you showed so far, except
for the raw data of one (why only one?!) side of the diff, is useless.

Thomas Rast
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to