[Top][All Lists]

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

PSPP-BUG: [bug #31561] SET PRINTBACK=OFF not effective for some output d

From: Ben Pfaff
Subject: PSPP-BUG: [bug #31561] SET PRINTBACK=OFF not effective for some output drivers
Date: Sat, 23 Apr 2011 05:37:15 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110323 Iceweasel/3.5.16 (like Firefox/3.5.16)

Follow-up Comment #1, bug #31561 (project pspp):

I pushed a few commits that fix up related issues:

commit 5d8fa2ae8c6e7d890570585aedec66bd51630814
Author: Ben Pfaff <address@hidden>
Date:   Fri Apr 22 22:29:19 2011 -0700

    ascii: Print syntax in output single-spaced.
    When SET PRINTBACK=ON was in effect, the ASCII output driver would
    put a blank line between successive lines of syntax, because each line
    was output separately.  This commit fixes that, by causing the output
    core to combine successive syntax output items into a single item that
    contains multiple lines of text.  This was essentially what the HTML
    output driver was doing anyhow, so putting this into the core also
    allows removing the corresponding logic from the HTML driver.

commit 0d70eff1e5dcd89a73f09ce6bc999ccbec8234b5
Author: Ben Pfaff <address@hidden>
Date:   Fri Apr 22 22:10:04 2011 -0700

    ascii: Don't print command names in output.
    This seems to be closer to what users expect.
    I think that having the command names in output was being confused
    by users with SET PRINTBACK=ON (see e.g. bug #31561) even though I
    really just added that so that there are clear titles for the output
    that goes with each procedure.  This change should help, I think.
    It might make sense to make drivers only print the titles of
    procedures that have other output, but this commit doesn't do that.

commit 3ffbc278e6bad8e4b83e28b5fda1a29d915e58c1
Author: Ben Pfaff <address@hidden>
Date:   Fri Apr 22 22:07:52 2011 -0700

    odt: Write command name in output both only before command, not after.

I haven't decided whether this is a sufficient fix yet, so I'm leaving the bug
open for now.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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