Re: longjmp in psql considered harmful

Martijn van Oosterhout wrote:
> On Sun, Jun 11, 2006 at 02:57:38PM -0400, Tom Lane wrote:
> > Martijn van Oosterhout <kleptog@svana.org> writes:
> > > As it states in the comment, you can't remove the longjump because
> > > it's the only way to break out of the read() call when using BSD signal
> > > semantics (unless you're proposing non-blocking read+select()). So the
> > > patch sets up the sigjump just before the read() and allows the routine
> > > to return. If you're not waiting for read(), no sigjump is done.
> > 
> > I think you're missing my point, which is: do we need control-C to
> > force a break out of that fgets at all?
> 
> If you're asking me, yes. I use it a lot and would miss it if it were
> gone. Is there another shortcut for "abort current command and don't
> store in history but don't clear it from the screen"?

M-#  (Note that it doesn't work in psql because it puts a # and not a
--.  But we could fix it.)

But it does store in history.  Why do you want it on the screen but not
in the history?