wdiff-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[wdiff-bugs] [bug #31291] wdiff -t exits with errorcode 1


From: Martin von Gagern
Subject: [wdiff-bugs] [bug #31291] wdiff -t exits with errorcode 1
Date: Thu, 21 Oct 2010 09:38:41 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.11) Gecko/20101020 Gentoo Firefox/3.6.11

Update of bug #31291 (project wdiff):

                  Status:                    None => Need Info              
             Assigned to:                    None => gagern                 

    _______________________________________________________

Follow-up Comment #1:

wdiff returning exit code 1 is correct, as the files do differ. Exit code 0
means no difference, and exit code 2 would indicate an error.

If you want to imply that ALL you get is the exit code, no display, then I
fail to reproduce this. I would welcome additional information, such as
* the wdiff version exhiobiting this problem
* your operating system and version
* your terminal application and version
* the value of your $TERM environment variable
* the output from "infocmp -1L"
* the config.log file generated when building wdiff
* the output from "ldd wdiff" if this is on Linux or similar
* do things work as expected without the -t?
* do things work when you supply -tK instead of only -t?

I assume that the way wdiff does terminal initialization and deinitialization
might be to blame. By default (i.e. without the -K), wdiff will send an
initialization string to the terminal which is intended for applications that
control cursor movement. wdiff doesn't do such movement, so it shouldn't
require that initialization. And I guess some terminals might restore the
state of the screen when leaving that terminal mode, which in most cases would
be when you leave an interactive application, but in this case might be
immediately after differences have been "displayed". So perhaps the reason you
see no output is that terminal deinitialization was too fast for it.

If that does indeed fix the problem, I'll consider making -K the default, and
dropping the option. Hopefully that won't cause ill effects on other machines.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31291>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]