Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-05 Thread Jim C. Nasby
On Sat, Mar 04, 2006 at 01:07:15PM -0500, [EMAIL PROTECTED] wrote: > For me, I prefer the interactive behaviour of ZSH. Multiline > statements remain as multiline statements, as they were typed. > One can navigate up and down through the multiline statement > to make alterations. The real beauty of

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Bruce Momjian
Just to clarify, is this the problem? test=> SELECT test-> \d No relations found. test-> 1; ?column? -- 1 (1 row) test=> SELECT \d 1; Did not find any relation named "1".

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Sergey E. Koposov
On Sat, 4 Mar 2006, Tom Lane wrote: > Has anyone else been finding the recent behavior of CVS-tip psql > to be a disimprovement? I've gotten sufficiently annoyed with it > that I'm ready to propose reverting this patch: > > 2006-02-11 16:55 momjian > > * src/bin/psql/: help.c, input.c, i

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Michael Paesold wrote: >> When you edit a multiline function in zsh, you can easily press Control-C, >> then type "man zsh", return, and press "up" to continue editing the >> function as it was left when you pressed Control-C. > Not sure about zsh's C

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Alvaro Herrera
Tom Lane wrote: > Has anyone else been finding the recent behavior of CVS-tip psql > to be a disimprovement? Another minor issue is that \s doesn't show copy-pastable things. For example: alvherre=# select 1 alvherre-# union all alvherre-# select 2; ?column? -- 1 2 (2 r

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Michael Paesold
Alvaro Herrera wrote: Michael Paesold wrote: When you edit a multiline function in zsh, you can easily press Control-C, then type "man zsh", return, and press "up" to continue editing the function as it was left when you pressed Control-C. Not sure about zsh's Ctrl-C, but in bash I press E

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Alvaro Herrera
Michael Paesold wrote: > When you edit a multiline function in zsh, you can easily press Control-C, > then type "man zsh", return, and press "up" to continue editing the > function as it was left when you pressed Control-C. Not sure about zsh's Ctrl-C, but in bash I press Esc-# and a # is prepe

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Michael Paesold
Tom Lane wrote: At a minimum this code has to be fixed to understand the difference between backslash commands and SQL lines, and not combine them in history entries; otherwise we should revert it. I'm leaning to "revert" since I haven't actually seen a case where pulling back multiple lines he

Re: [HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread mark
On Sat, Mar 04, 2006 at 12:08:25PM -0500, Tom Lane wrote: > Comments? I generally do not use psql in this manner, because I've found it to be annoying before the change. After the change, from what you describe, I too would find it annoying still. For me, I prefer the interactive behaviour of ZSH

[HACKERS] Not so happy with psql's new multiline behavior

2006-03-04 Thread Tom Lane
Has anyone else been finding the recent behavior of CVS-tip psql to be a disimprovement? I've gotten sufficiently annoyed with it that I'm ready to propose reverting this patch: 2006-02-11 16:55 momjian * src/bin/psql/: help.c, input.c, input.h, mainloop.c, prompt.c, tab-complet