Topic: Command mode line editing after accessing Help (1 of 7), Read 37 times
Conf: VEDIT Macro Language Support
From: Gary Darsey
Date: Thursday, August 26, 2004 08:43 AM

I have noticed the following: while entering/editing a command mode window command line, if the online help is accessed and then the command line is returned to for more editing, the mode is only overstrike and the cursor keys don't move the cursor. I often access the Help while entering commands, and I find I need to recall the line and start over. Is there any simple way to fix this behavior?

I'm using VEDIT 6.13.1 7/14/2004 under Win 2K Pro, but I noticed this also with VEDIT 6.12.1 5/24/2004.

 


Topic: Re: Command mode line editing after accessing Help (2 of 7), Read 23 times
Conf: VEDIT Macro Language Support
From: Christian Ziemski
Date: Thursday, August 26, 2004 11:41 AM

On Thu, 26 Aug 2004 08:43:00 -0400, Gary Darsey wrote:

>I have noticed the following: while entering/editing a command
>mode window command line, if the online help is accessed and
>then the command line is returned to for more editing, the mode
>is only overstrike and the cursor keys don't move the cursor.

The same problem happens when switching to another application and
back while in command mode. (Hmmm, the help *is* another app.)

I reported that to Ted in January, but it seems to be difficult to
replicate. At least on Ted's computers that didn't happen.

While playing around with it (I still can replicate it here) I found a
workaround:

When the cursor is stuck in the command line try pressing the keys
[Begin] [End] on your keyboard.
I don't know the exact English names for those keys. They are the both
middle ones in the sixpack, between [Ins],[Del] and [PgUp],[PgDn].

Christian

 


Topic: Re: Command mode line editing after accessing Help (3 of 7), Read 23 times
Conf: VEDIT Macro Language Support
From: Gary Darsey
Date: Thursday, August 26, 2004 11:49 AM

Yes, Christian, that does work. In English these are the [Home] and [End] keys. It does "unlock" the line editing mode. Also, just minimizing VEDIT causes the same behavior; going to another application isn't even needed.

Thanks!

-Gary

 


Topic: Re: Command mode line editing after accessing Help (4 of 7), Read 28 times
Conf: VEDIT Macro Language Support
From: Ted Green
Date: Monday, September 06, 2004 01:52 PM

At 11:42 AM 8/26/2004, you wrote:
>>I have noticed the following: while entering/editing a command
>>mode window command line, if the online help is accessed and
>>then the command line is returned to for more editing, the mode
>>is only overstrike and the cursor keys don't move the cursor.
>
>The same problem happens when switching to another application and
>back while in command mode. (Hmmm, the help *is* another app.)

It is fixed in VEDIT 6.13.

Ted.

 


Topic: Re: Command mode line editing after accessing Help (5 of 7), Read 14 times
Conf: VEDIT Macro Language Support
From: Gary Darsey
Date: Friday, December 03, 2004 01:18 PM

I changed jobs and have just downloaded VEDIT 6.12.1 from the website. How do I get the latest 6.13 version that has this command line mode editing (and Dir_Date()) problems fixed?

Thanks!

-Gary Darsey

 


Topic: Re: Command mode line editing after accessing Help (6 of 7), Read 16 times
Conf: VEDIT Macro Language Support
From: Ted Green
Date: Friday, December 03, 2004 01:38 PM

At 01:18 PM 12/3/2004, you wrote:
>From: "Gary Darsey"
>
>I changed jobs and have just downloaded VEDIT 6.12.1 from the website. How do I get the latest 6.13 version that has this command line mode editing (and Dir_Date()) problems fixed?

VEDIT 6.13 is still a beta and can be downloaded from:

http://www.vedit.com/download/beta/vw-pro64.exe

Ted.

 


Topic: Re: Command mode line editing after accessing Help (7 of 7), Read 10 times
Conf: VEDIT Macro Language Support
From: Ted Green
Date: Friday, January 07, 2005 06:24 PM

At 07:52 AM 8/27/2004, you wrote:
>>>I have noticed the following: while entering/editing a command
>>>mode window command line, if the online help is accessed and
>>>then the command line is returned to for more editing, the mode
>>>is only overstrike and the cursor keys don't move the cursor.
>>
>>The same problem happens when switching to another application and
>>back while in command mode. (Hmmm, the help *is* another app.)

This is fixed in 6.13.

Ted.