Assigning a debug action to a PFkey is problematic on J9.02 because of
some internal technical details. Briefly, the debug action now produces
a result that must be received by the suspension code, but the normal
ways of running PFkeys cause the verb result to be discarded.
Perhaps a future JQt will fix this problem. In the meantime I can offer
a butt-ugly workaround:
If you now have:
F3;0;Run;dbrun $0
replace it with the ONE LINE
F3;0;Run;9!:29 (1) [ 9!:27 'dbrun $0 [ 9!:29 (' , (": 9!:28'') , ') [
9!:27 ''' , ((#~ [: >: ''''&=) 9!:26'') , ''''
This pushes the sentence through the immex phrase to where suspension
will see its result.
Henry Rich
-------- Forwarded Message --------
Subject: [Jprogramming] Brave GitHub Rewards and dbrun ''
Date: Mon, 30 Nov 2020 08:57:28 -0700
From: John Baker <[email protected]>
Reply-To: [email protected]
To: Programming forum <[email protected]>
I just noticed that if you are on GitHub you can register for Brave browser
token rewards.
The tokens can be used to tip sites and can be converted into cash. Nobody
will get rich on them but hey it's free money. Jsoftware might as well
register.
Also, have recent changes to QT altered how PFKEYS work? For years I have
assigned dbrun '' to a PFKEY. Then to debug I set all the stops with
dbstop 'whatever' and simply hit the PFKEY to step through explicit code.
It's simple and effective but it stopped working with the last round of
changes. Now I must type dbrun'' in the console.
Cheers
--
John D. Baker
[email protected]
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
