Hi,
Aaron wrote:
> Steve sent these to me in a separate message and they are now in
> this directory
>
> http://www.cs.bham.ac.uk/research/poplog/leach-utils/
>
> in a small tar file
>
> http://www.cs.bham.ac.uk/research/poplog/leach-utils/vedutils.tar.gz
Good, I'm not sure how/if to do the 'key-bindings'.
But first please correct possible misunderstandings:
Steve wrote:
> define do_ved_add( L );
> lvars col = vedcolumn;
> ....
> enddefine;
? So this is the 'little command language interpreter',
which eg. interprets the "for" structure by running
define ved_add_for();
[ 'lvars ' + ';' nl 'for in do' nl 'endfor;' - ] .do_ved_add
enddefine;
and inserts the required text. I confirmed this.
OK, I see that the above is a simplified subset of:
ved_add_for.p
But even if I used the expanded/refined ved_add_for(); ,
I still need to bind a key to activate the short cut ?
I'm guessing that I would use something like:
vedsetkey(key>, <corresponding proc:eg. ved_add_for() >);
Well no !
Modifying my existing F12 key-mapping to:
define :ved_runtime_action;
.......
vedsetkey('\^[[24~', ved_add_for());
enddefine;
And compile/run, gives me:-
1. mishap - ste STACK EMPTY
line <after the modified line>
2. The "for" structue is written at the cursor !!?
I'm not using poplog these days, so I don't have time and skill
to investigate/debug this.
-- Chris Glur.
|