| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Michael Paesold <mpaesold(at)gmx(dot)at> |
| Cc: | mark(at)mark(dot)mielke(dot)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-04 20:35:39 |
| Message-ID: | 20060304203539.GB13230@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
prepended to the current line and entered into the history. This is
what I use when I want to review some manpage or something.
It also "works" in psql, but unsurprisingly it also prepends #. We
could fix it by having it prepend -- instead, or maybe enclose the
current editing buffer in /* */.
(This only works in a single line fashion in bash, but I don't see why
we couldn't make it work multiline in psql.)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paesold | 2006-03-04 20:54:41 | Re: Not so happy with psql's new multiline behavior |
| Previous Message | Tom Lane | 2006-03-04 19:49:56 | Re: EXPLAIN and HashAggregate |