On Wed, Dec 18, 2019 at 4:11 PM Tom Lane wrote:
>
> I wrote:
> > Pavlo Golub writes:
> >> I cannot find the reason why EDITOR value on Windows is quoted.
>
> > The comment you quoted explains it: apparently people expect
> > paths-with-spaces to work in that value without any manual quoting.
>
>
I wrote:
> Pavlo Golub writes:
>> I cannot find the reason why EDITOR value on Windows is quoted.
> The comment you quoted explains it: apparently people expect
> paths-with-spaces to work in that value without any manual quoting.
Actually, after digging in the git history and archives, the
Pavlo Golub writes:
> I cannot find the reason why EDITOR value on Windows is quoted.
The comment you quoted explains it: apparently people expect
paths-with-spaces to work in that value without any manual quoting.
> One may force quote env var if he wants to.
Given the lack of prior
Hello.
I cannot find the reason why EDITOR value on Windows is quoted. It
should not be. One may force quote env var if he wants to.
Right now, for example, one cannot use sublime, since to use it in a
proper way you should
SET EDITOR="C:\Program Files\Sublime\subl.exe" --wait
The problem can
