octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with copy/paste from/to Qt command Window


From: Daniel J Sebald
Subject: Re: Help with copy/paste from/to Qt command Window
Date: Mon, 22 Apr 2013 16:04:10 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 04/22/2013 03:49 PM, PhilipNienhuis wrote:
Daniel Sebald wrote
On 04/22/2013 02:54 PM, John W. Eaton wrote:
What needs to be done to enable copying text from or pasting text to the
Qt command window?

What should we do about the conflict with the customary Windows
keybinding for Ctrl-C to copy text vs. using that to generate an
interrupt?

I think it would be acceptable to have Ctrl-C interrupt when Octave is
executing commands in the interpreter and otherwise copy text, but it's
not clear to me how to switch keybindings. Can someone with Qt
experience comment?

Make it configurable, perhaps.  The default should probably be that if
the terminal window is in focus, Ctrl-C will break the Octave process
back to the command line.  If focus is somewhere outside the terminal
window, Ctrl-C could always mean copy.  Cntrl-V would still mean paste
inside the terminal window.  There is a right mouse click menu item
having copy and paste entries.

My suggestion was and is more or less what John mentioned above:
(if the command window has focus:) Ctrl-C to interrupt Octave when it is at
work, otherwise copy highlighted/selected text from the command window.
I think it goes without saying that in order to copy something from a window
or pane, that window or pane must have focus anyway.

Eh, I don't know. Sounds good as a convenience, until put into practice. I don't think a key's behavior should change too drastically, if at all, based upon state. Say the user is used to using Cntrl-C as copy, then runs a long batch job that might take five minutes. While that's going the user starts working away in the editor and inadvertently types a Cntrl-C in the terminal window and it stops the process because of it's change in behavior. The user probably won't be happy. Can set it up that way, then let developers try it out for a while.


AFAIK the vast majority of Windows programs already work that way, with the
notable exception of the cmd32.exe terminal/console.
Even more, may GUI programs on Linux already use Ctrl-C, Ctrl-X and Ctrl-V
as well.


A configuration in the Peferences... could make Cntrl-C mean "copy what
is highlighted" in the terminal window.  Of course, the center mouse
button (for those who still use one) works for non-clipboard copying.
If that is an option, then there would have to be some menu selection or
icon for breaking out of the Octave process.  That should actually be a
set of functions in a "run" group, "run" not being totally worked out
just yet.

I find it hard to follow what you mean to say here, apologies.

To make things configurable would be great - but IMO that is no priority.

All I meant was, if the user configures the GUI so that Cntrl-C doesn't mean break in the terminal window, there needs to be some other means to break Octave out of what it is doing (other than exit). For example, say there is something under "Debug" menu or under a new menu called "Run" called "break" that will perform the same as what Cntrl-C would normally do.

Dan


reply via email to

[Prev in Thread] Current Thread [Next in Thread]