[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Text output and WIDTH
From: |
Ben Pfaff |
Subject: |
Re: Text output and WIDTH |
Date: |
Wed, 8 Jan 2020 23:28:46 -0800 |
The use of SET WIDTH was buggy. It should be fixed now.
I think it's likely that Frans was outputting to a file. I don't see
problems with using the width of the terminal on Linux. (On Windows, I
guess it probably doesn't work, because I doubt Windows has the right
ioctl. I guess that there is some Windows-specific magic to find out
the terminal width, but PSPP doesn't know about it.)
On Tue, Jan 7, 2020 at 11:21 PM John Darrington
<address@hidden> wrote:
>
> I thought that SET WIDTH should also work.
>
> Also I thought that when run interactively from a terminal, it should
> default to the width of the terminal.
>
> Perhaps we need to investigate why this is not happening.
>
> J'
>
>
> On Mon, Jan 06, 2020 at 09:58:59PM -0800, Ben Pfaff wrote:
> On Mon, Jan 6, 2020 at 12:54 PM Frans Houweling <address@hidden> wrote:
> > is there any way to prevent text output to wrap at 80 columns?
> > I would like to retrieve cluster centers from the output of QUICK
> > CLUSTER, but this is hindered by wrapping:
>
> Yes, you can specify the maximum output width with "-O width=200" on
> the command line for 200 columns (or whatever width you like).
- Text output and WIDTH, Frans Houweling, 2020/01/06
- Re: Text output and WIDTH, Ben Pfaff, 2020/01/07
- Re: Text output and WIDTH, Frans Houweling, 2020/01/07
- Re: Text output and WIDTH, John Darrington, 2020/01/08
- Re: Text output and WIDTH, Frans Houweling, 2020/01/08
- Re: Text output and WIDTH, Ben Pfaff, 2020/01/09
- Re: Text output and WIDTH, Frans Houweling, 2020/01/09
- Re: Text output and WIDTH, Ben Pfaff, 2020/01/09
- Re: Text output and WIDTH, Frans Houweling, 2020/01/09
- Re: Text output and WIDTH, Ben Pfaff, 2020/01/10
- Re: Text output and WIDTH,
Ben Pfaff <=