Re: closing a macro completely upon connect

Ya all 'macros' that we talked about were definitions. Not simple
reassignment of keys.
You mentioned 'temporarly' enters the command window. Could you clarify on
that.

basically:
set key \96 \Ktest

define test {
......
connect
return
}

this is how all my macro definitions work, and are successful when used in
connect mode. This design makes it temporary.
By the way, if I did have Jeff's patch, what would my patch version be?
2.1.4?



"Frank da Cruz" <fdc@xxxxxxxxxxxx> wrote in message
news:slrne1rfs1.mj2.fdc@xxxxxxxxxxxxxxxxxxxxxxxxx
On 2006-03-19, Frank da Cruz <fdc@xxxxxxxxxxxx> wrote:
: On 2006-03-15, Scott Caissie <scottac@xxxxxxxxxxxxxxx> wrote:
:: Can you clarify your own posts? A few things are bothering me still.
::
:: Macros only execute in "command mode". Its been several years since I
:: fixed the bug associated with SET KEY and terminal mode, but my
:: recollection is that the macro would be configured to execute and
:: "terminal or connect mode" would not be exited.
::
: I hope I can clarify this by saying that keystroke macros should be able
to
: run in either Command mode or Connect mode, but currently don't due to
the
: aforementioned bug. But when you invoke a macro with a keystroke while
in
: Connect mode, K95 temporarily enters Command mode to execute it, because
: that's where commands are executed, and a macro is just a series of
commands.
:
: When you assign something to a key with SET KEY, it can be a character
or
: string to be transmitted to the host, or a Kverb, or a macro invocation.
The
: first two are executed directly in Connect mode, the latter can be
executed
: only in Command mode. You can mix all of these things in a single key
: definition. I presently don't have a version of K95 handy without the
bug,
: so I can't say exactly how this appears to the user; there might or
might not
: be some visible transitions on the screen.
:
Upon rereading this, I see I should make one more clarification. The word
"macro" is vague. Keystroke macros are often understood to be assignments
of
characters or strings to a key. That's not what we're talking about here.
There is no bug in Kermit 95 in this respect. The bug involves only the
assignment of a Kermit macro invocation to a key. For example:

define somemacro xxx, yyy, zzz

(where xxx, yyy, and zzz is a list of one or more Kermit commands). This
macro can be assigned to (say) the F11 key as follows:

set key \378 \Ksomemacro

or:

set key \378 \K{somemacro}

This looks like a Kverb but it isn't. As long as the string following the
\K
is not the name of a built-in Kverb, it is looked up in Kermit's macro
table
and, if found, executed (by internally switching to command mode
temporarily).
This is what does not work when the key is pressed while in Connect mode
(because of the bug). It still works when the key is pressed while in the
Command screen. The bug is fixed in Jeff's copy:

http://www.columbia.edu/kermit/support.html

but I can't distribute that yet, until some arrangements have been made
between Columbia University and Jeff, which are taking a long time. In
the
meantime, it is available directly from Jeff as described on the page
linked
to above.

- Frank


.

Relevant Pages

  • Re: MoveRight in table fails at 1%: bug? workaround?
    ... temporary files as your macro runs, so that all changes can be undone. ... about erros at Selection.MoveRight command? ... >> Does anyone know something like a known bug about MoveRight? ... Using the Selection object makes for more convoluted ...
    (microsoft.public.word.vba.general)
  • Re: Display New Document task pane
    ... Well, since you have assigned a macro to the command whose ID is 18, it ... I do acknowledge that the .Execute command works whether the commandbar is ... button and still have the New Document task pane show: ... create a new toolbar called Hidden. ...
    (microsoft.public.word.vba.general)
  • Re: Display New Document task pane
    ... that custom macro will run when you execute that command. ... button and still have the New Document task pane show: ... create a new toolbar called Hidden. ...
    (microsoft.public.word.vba.general)
  • Re: closing a macro completely upon connect
    ... fixed the bug associated with SET KEY and terminal mode, ... invoking a macro as a kverb works. ... interactively from the command prompt. ... A macro mapped to a key will not execute if you enter CONNECT mode ...
    (comp.protocols.kermit.misc)
  • Re: alt x oddity
    ... The bug and the fix is so vague. ... commands) and use that macro about a hundred times or so, ... Error #2 looking at the COMMAND window with a flashing cursor. ...
    (comp.protocols.kermit.misc)