On Thu, Jan 24, 2019 at 10:03:12AM -0500, Tom Lane wrote:
> Francisco Olarte <folarte@peoplecall.com> writes:
> > On Thu, Jan 24, 2019 at 10:33 AM <rodrigo_de_carlos@yahoo.com> wrote:
> >> I used the \watch option in psql and couldn’t stop the loop until I found the way* using ctrl-c. I am new to
programming,and perhaps using ctrl-c is standard practice, but in a future manual perhaps you should replace the text
below‘until interrupted’ with ‘until interrupted (using ctrl-c)’.
>
> > Ctrl-C, AFAIK, sends the INT(errupt) signal in *ix, which normally
> > stops looping things. That's the standard way to interrupt long
> > running commands, send them the interrupt signal.
>
> > IIRC windows does similar stuff, although I think Ctrl-break had to be
> > used, but I haven't used it since the dawn of the century.
>
> Yeah, the reason that the message doesn't already mention control-c
> is that the interrupt signal varies depending on platform (also,
> it's possible to remap it to some other key, on most platforms).
> In the end we expect you to know that much about whatever environment
> you're using.
Well, in psql we ended up just suggesting the likely default for exiting
psql:
#ifndef WIN32
puts(_("Use control-D to quit."));
#else
puts(_("Use control-C to quit."));
#endif
Not sure if we could do the same thing here.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
