Messed up - I mean when going "up" and scrolling command history it
shows long queries (eg 2 line long) in single line and the exceeding
part overwrites the beginning of the query), or when writing long SQL
at some point I'm starting to overwriting it from the beginning of the
line.
Sometimes whe
Gregory Stark <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> I can confirm that when the pager is open, psql does not resize
>> properly. Maybe psql is ignoring signals while the pager is open, or
>> something.
> Hm, system() is documented to ignore SIGINT and SIGQUIT
>> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>
>> > I can confirm that when the pager is open, psql does not resize
>> > properly. Maybe psql is ignoring signals while the pager is open, or
>> > something.
Hm, system() is documented to ignore SIGINT and SIGQUIT I wonder if it's
(erroneously?) i
Tom Lane escribió:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I can confirm that when the pager is open, psql does not resize
> > properly. Maybe psql is ignoring signals while the pager is open, or
> > something.
>
> If the pager is running, psql's not going to do anything anyway, no?
> W
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> How do you know that the pager is in the same process group? Is the
> process group something that's inherited automatically on fork()?
It certainly should be.
> I can confirm that when the pager is open, psql does not resize
> properly. Maybe psql i
Gregory Stark escribió:
> Hm, this Bash FAQ seems to indicate this shouldn't be a problem -- the whole
> process group is supposed to get the window size. Psql isn't doing the job
> control stuff the FAQ entry talks about so the pager ought to be in the same
> process group. So I'm puzzled.
How d
On Mon, Oct 27, 2008 at 3:59 AM, wstrzalka <[EMAIL PROTECTED]> wrote:
> I'm using psql mainly in putty window.
>
> I have a problem while resizing the window.
> When changing the window size (and those chars per row) psql output
> becomes mess, the only rescue is to exit and run the psql again. It
Gregory Stark <[EMAIL PROTECTED]> writes:
> Could you define "messed up"?
>
> What I see is that the query output is formatted correctly but readline still
> thinks the screen is the old size. (This is in CVS HEAD -- this code was
> definitely different in 8.3 and before so the behaviour may be
wstrzalka <[EMAIL PROTECTED]> writes:
> On 27 Paź, 13:16, [EMAIL PROTECTED] (Sam Mason) wrote:
>> On Mon, Oct 27, 2008 at 01:59:42AM -0700, wstrzalka wrote:
>>
>> > When changing the window size (and those chars per row) psql output
>> > becomes mess, the only rescue is to exit and run the psql a
On 27 Paź, 13:16, [EMAIL PROTECTED] (Sam Mason) wrote:
> On Mon, Oct 27, 2008 at 01:59:42AM -0700, wstrzalka wrote:
> > I'm using psql mainly in putty window.
>
> it's pretty much always just worked with me. I'm using a very old
> version of putty, but it all hangs together as well as anything els
On Mon, Oct 27, 2008 at 01:59:42AM -0700, wstrzalka wrote:
> I'm using psql mainly in putty window.
it's pretty much always just worked with me. I'm using a very old
version of putty, but it all hangs together as well as anything else
does
> When changing the window size (and those chars per row
wstrzalka wrote:
I'm using psql mainly in putty window.
I have a problem while resizing the window.
When changing the window size (and those chars per row) psql output
becomes mess, the only rescue is to exit and run the psql again. It
looks like it's initializing the output params at startup an
I'm using psql mainly in putty window.
I have a problem while resizing the window.
When changing the window size (and those chars per row) psql output
becomes mess, the only rescue is to exit and run the psql again. It
looks like it's initializing the output params at startup and don't
refresh it
13 matches
Mail list logo
