Topic: Can't search for blank line in a macro (1 of 3), Read 47 times
Conf: Keyboard, keystroke macros
From: Michael Lang
Date: Sunday, February 02, 2003 12:08 PM

A couple of years ago, I wrote a little macro, which searches for the
next paragraph. This works fine in Vedit for DOS, but it doesn't work
under the Windows version. The problem seems to be:
Alt-Cursor-Right [SEARCH]|L|L. This produces the prompt
"Search: |L|L" under DOS Vedit, but under WinVedit I get: "Search:
it seems to be a bug. If it is, I'd be pleased, if it could be fixed
soon, I use version 6.03.3.

<*** Michael Lang ***>

 


Topic: Re: Can't search for blank line in a macro (2 of 3), Read 46 times
Conf: Keyboard, keystroke macros
From: Christian Ziemski
Date: Sunday, February 02, 2003 02:04 PM

>From: "Michael Lang"
>
>A couple of years ago, I wrote a little macro, which searches for the
>next paragraph. This works fine in Vedit for DOS, but it doesn't work
>under the Windows version. The problem seems to be:
>Alt-Cursor-Right [SEARCH]|L|L. This produces the prompt
>"Search: |L|L" under DOS Vedit, but under WinVedit I get: "Search:
>
That seems to be a problem with the keyboard handling in german
Windows versions. I tried it with Windows2000/SP6.

All keys reached via AltGr (resp. Ctrl-Alt) are affected.

Example:

in VEDIT.KEY : [SEARCH]@ ~ {|} [\]
in Search-box : qm + 7<0 89

After switching the keyboard driver to "english" all works fine.

As workaround you can use:
Alt-Cursor-Right [VISUAL EXIT] Search("|L|L", ADVANCE)



(Ted: We exchanged several mails in Sept. 2001 (6.0 beta) about german
keyboard problems. I sent you some pictures and tables. Perhaps that's
related.)


Christian

 


Topic: Re: Can't search for blank line in a macro (3 of 3), Read 44 times
Conf: Keyboard, keystroke macros
From: Ted Green
Date: Monday, February 03, 2003 01:12 PM

At 02:30 PM 2/2/2003, you wrote:

>As workaround you can use:
>Alt-Cursor-Right [VISUAL EXIT] Search("|L|L", ADVANCE)

Thank you for the detailed reply Christian.

We highly suggest using the macro language, as above, instead
of "keystroke macros".

I eventually want to automatically convert recorded keystroke
macros into the equivalent macro language commands.

Ted.