Re: q for quit in plot windows

[<tim...@en...>]

> Timothée Lecomte wrote:
>>>The ctrl-c copy was easy enough.  Just replace "c" with "ctrl-c"...
>>>
>>>Anyway, I see when typing 'h' for a plot to get the key bindings there
>>> are
>>>these
>>>two at the very top (i.e., follow the button description):
>>>
>>>
>>>  Space          raise gnuplot console window
>>>  q            * close this X11 plot window
>>>
>>>[snip]
>>>
>>>               * indicates this key is active from all plot windows
>>>
>>>I'm assuming that by the use of term->(function) the mouse/keyboard
>>>interface is
>>>meant to be very general and not restricted to X11.
>>
>>
>>
>> I will try not to repeat what was said by Ethan and Petr, but here are
>> my
>> thoughts on this:
>>
>> "raise console" and "quit plot window" do not go through the event
>> system
>> (because they predate it), they are handled directly by the terminal.
>> That's why ' ' and 'q' are keys that you cannot bind to something else,
>> with the exception of the 'ctrl-q' option in x11 and wxt.
>
> Right, but the question is why must the documentation for 'q' and ' ' be
> special, sitting out on its own?  Why can't the 'q' and ' ' simply be
> placed in
> the bindings documentation?

They are. Quote:
 "By default, the <space> hotkey raises gnuplot's command window. On some
 terminals (e.g. x11, wx, pm), 'q' closes the graph window. These defaults
can
 be changed to ctrl-space and ctrl-q by starting gnuplot as 'gnuplot -ctrlq',
 see `x11 command-line-options`, or by the X Resource 'gnuplot*ctrlq'.
 Note: if <space> (or ctrl-space) does not raise the gnuplot window under
X11,
 see discussion in `raise`."

>
> As you explained, the mouse-in-only-one-window limitation came back to me,
> so
> that is why the asterisk.  Yet, some would consider the
> mouse-in-only-one-window
> a bug in itself.
>

Admittedly. This is another topic though.

>
>> There's no term->close right now, nor is there a term->raiseconsole (and
>> that's fortunate, since raising _gnuplot console_ is not the _plot
>> window_
>> business).
>
> Petr would think otherwise, I'm guessing from his past posts.  There is
> the
>
>      set term x11 close
>
> which could be bound to a key.
>
>
>> Wow, what a long message... Don't hesitate to comment.
>
> No comment on specific terminal implementations, only that it seems easy
> to fix this.

I'll repeat myself, maybe you lost it in the noise of my message: The easy
fix means a big regression; 'q' and ' ' would not always work anymore, but
only when the terminal is the active one.

>
> Dan