from
finddissectline_dissect_
there appears to be some magic with
WinSelect_jqtide_
WinText_jqtide_
but accessing these seem to get stale quickly. ie. doesn't grow despite more
getting added to console
this line does update a new "winselect" but it seems out of sync
(400 (i.@[ + -~) 0 {.@". fs) {ft [ 'ft fs' =. {:"1 wd 'sm get term;'
should print the last 400 characters, but
(0 ". fs), #ft [ 'ft fs' =. {:"1 wd 'sm get term;'
94123 94123 160296
(0 ". fs), #ft [ 'ft fs' =. {:"1 wd 'sm get term;'
94238 94238 160370
(0 ". fs), #ft [ 'ft fs' =. {:"1 wd 'sm get term;'
94312 94312 160444
(0 ". fs), #ft [ 'ft fs' =. {:"1 wd 'sm get term;'
94386 94386 160518
the last select value is well below the character count. These are 4
successive calls. Select does not go up by a consistent amount and neither
does Textcount, though in the last 2 calls there is a consistent 76 increase in
select and 72 increase in Text
If I were to guess what is happening, for the large discrepancies, is any
output from 1!:2 does not update fs.
I can point out that finddissectline_dissect_ as a user key breaks fairly
quickly after starting jqt. Though it does work on startup.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
