| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Windows v readline |
| Date: | 2020-01-03 08:06:10 |
| Message-ID: | 6a4eec83-dbb4-65a8-319e-03c29ef6d94a@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-12-30 14:28, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> On 2019-09-29 22:55, Andrew Dunstan wrote:
>>> It would certainly be nice to have readline-enabled psql on Windows if
>>> possible.
>
>> I tried this out. First, it doesn't build, because readline doesn't do
>> the dllimport/dllexport dance on global variables, so all references to
>> rl_* global variables in tab-complete.c fail (similar to [0]). After
>> patching those out, it builds, but it doesn't work.
>
> What do you mean by "patching those out" --- you removed all of
> tab-complete's external variable assignments? That would certainly
> disable tab completion, at a minimum.
Yeah, basically remove tab completion altogether. But readline would
still be useful without that for line editing and history.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2020-01-03 08:08:13 | Re: parallel vacuum options/syntax |
| Previous Message | Amit Kapila | 2020-01-03 08:05:54 | Re: parallel vacuum options/syntax |