Re: Getting psql to redisplay command after \e
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2019-11-22T22:10:24Z
Lists: pgsql-hackers
I wrote: > Fabien COELHO <coelho@cri.ensmp.fr> writes: >> This suggests that readline cannot be used to edit simply a known string? >> :-( "rl_insert_text" looked promising, although probably not portable, and >> I tried to make it work without much success anyway. Maybe I'll try to >> investigate more deeply later. > I think that rl_insert_text and friends can probably only be used from > readline callback functions. So in principle maybe you could make it > work by having an rl_startup_hook that injects text if there is any > to inject. There would remain the issues of (a) is it portable across > a wide range of readline and libedit versions, (b) will the prompting > behavior be nice, and (c) do we really want this to work fundamentally > differently when readline is turned off? I thought maybe you were going to work on this right away, but since you haven't, I went ahead and pushed what I had. There's certainly plenty of time to reconsider if you find a better answer. regards, tom lane
Commits
-
Make psql redisplay the query buffer after \e.
- d1c866e57f11 13.0 landed