| From: | Bernhard Herzog <bh(at)intevation(dot)de> |
|---|---|
| To: | Ian Barwick <barwick(at)gmx(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: psql slash command '\G' |
| Date: | 2002-03-26 10:27:33 |
| Message-ID: | 6qofhbtyi2.fsf@abnoba.intevation.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Ian Barwick <barwick(at)gmx(dot)net> writes:
> Peter Eisentraut writes:
> > Propose a macro processor.
>
> Why? What do you envisage? What advantages would this, and presumably the fair
> amount of additional and / or re-coding associated, have for me (or anyone
> else) compared to a more specific solution as suggested below?
If you've compiled psql with readline you could just use readline's
macro system. With e.g.
$if Psql
"\M-g": "\\x\\g\\x"
$endif
in your .inputrc, Meta-g would expand to \x\g\x
Bernhard
--
Intevation GmbH http://intevation.de/
Sketch http://sketch.sourceforge.net/
MapIt! http://www.mapit.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-03-26 13:08:31 | Re: build of 7.2.1 on SCO Openserver and Unixware 7.1.1 |
| Previous Message | Nicolas Bazin | 2002-03-26 06:21:31 | build of 7.2.1 on SCO Openserver and Unixware 7.1.1 |