×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Wow... thanks Buck!
I will try that... there is a "comfort level" with seeing the line numbers that I will need to get over.
Greg
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Monday, January 26, 2015 4:51 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] CTRL-C issue
On 1/26/2015 3:34 PM, Greg Wilburn wrote:
Buck,
I know I can "get around" this, but to me it's an issue. I shouldn't have to be that exacting when selecting rows for a copy. CTRL-C should be CTRL-C no matter where the cursor is positioned within the source member.
I agree. My reply wasn't intended to convince you to change your muscle
memory. After learning that Ctrl-Insert performs the copy all the time,
I figured I'd share that information in case someone were motivated to
tinker the keyboard shortcuts in the hopes of finding which (if?) of the
many 'When:' states is covered by the prefix area.
Preferences > General > Keys
Alternately, what about dropping the troublesome prefix area altogether?
I myself don't use the line numbers for much of anything except during
debugging.
Escape (to get to the command line) set prefixArea off
Again, to be clear, I'm not suggesting that my way is better. I'm
replying to you of course, but I'm also thinking of the archives and the
lurkers who might be following this thread.
midrange.com
