On 12/28/21 14:53, Tom Lane wrote:
> Matheus Alcantara <msalcantara....@pm.me> writes:
>>> it is not consistent with other \g* commands. Maybe a new statement \senv ?
>>> But what is the use case? You can just press ^z and inside shell write echo
>>> $xxx, and then fg
>> I think that the basic use case would be just for debugging, instead call
>> \getenv and them \echo, we could just use \getenv. I don't see any other
>> advantages, It would just be to
>> write fewer commands. I think that ^z and then fg is a good alternative,
>> since this behavior would be inconsistent.
> You don't even need to do that much. This works fine:
>
> postgres=# \! echo $PATH
>
> So I'm not convinced that we need another way to spell that.
> (Admittedly, this probably doesn't work on Windows, but
> I gather that environment variables are less interesting there.)
>
>
I haven't tested, but I'm fairly sure
postgres=# \! echo %PATH%
would do the trick on Windows.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
