From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | mark(at)mark(dot)mielke(dot)cc |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Not so happy with psql's new multiline behavior |
Date: | 2006-03-05 23:34:24 |
Message-ID: | 20060305233424.GG80721@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 04, 2006 at 01:07:15PM -0500, mark(at)mark(dot)mielke(dot)cc 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 this approach comes up
> when doing something such as defining a function. Would you
> LOVE the ability to edit the function, in the original form,
> as originally typed, allowing you to insert text, and even
> newlines into the middle? Effectively you have have a full
> text editor, for the last complete series of lines.
<snip>
> Oh no. We typed the wrong command in. It isn't 'a' we want. We want 'ls'.
>
> Hit up-arrow twice, and we get (_ = cursor)
>
> $ f()
> {
> a
> }_
ISTM this is much more useful than the way psql used to work. Don't know
about what's happening in -tip...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-03-06 02:09:36 | Re: LDAP auth |
Previous Message | Jim C. Nasby | 2006-03-05 23:28:29 | Re: ACCESS EXCLUSIVE LOCK |