bugwdiff - Bugs: bug #31291, wdiff -t exits with errorcode 1


bug #31291: wdiff -t exits with errorcode 1

Submitter:  Voker F. Seventh <voker57>
Submitted:  Sun 10 Oct 2010 09:11:19 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  gagern
Originator Name:  Open/Closed:  Closed
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:
       No canned response available


Mon 06 Dec 2010 06:27:27 PM UTC, comment #2: 

Should be fixed in wdiff 0.6.5 released yesterday. Please reopen and provide additional data if this doesn't fix this issue for you.

Martin von Gagern <gagern>
Project Administrator
Thu 21 Oct 2010 09:38:40 AM UTC, 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.

Martin von Gagern <gagern>
Project Administrator
Sun 10 Oct 2010 09:11:19 AM UTC, original submission:  
Voker F. Seventh <voker57>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by gagern (Posted a comment)
  • -email is unavailable- added by gagern
  • -email is unavailable- added by voker57 (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-12-06 gagern StatusNeed Info Fixed
        Open/ClosedOpen Closed
    2010-10-21 gagern StatusNone Need Info
        Assigned toNone gagern
        Carbon-Copy- Added gagern

    Back to the top

    Powered by Savane 3.9