You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RIDE protocol does now pass TRACE and MONITOR bits for edit/trace windows, whereas it only used to pass STOP bits though.
Editor deletes ⎕TRACE and ⎕MONITOR points when function was fixed with 2 ⎕FIX 'file://...' This happens only when using the RIDE protocol, and not when using the Windows IDE or the Linux TTY version.
Repro:
(⊂' res←foo arg''⍝ this is foo''res←arg''res←''foo'' arg') ⎕NPUT'/tmp/foo.aplf'12⎕FIX'file:///tmp/foo.aplf'
{(12⎕STOP⍵)(23⎕TRACE⍵) (13⎕MONITOR⍵)}'foo'122313
{( ⎕STOP⍵)( ⎕TRACE⍵) (⊣/⎕MONITOR⍵)}'foo'122313⎕ED'foo'⍝ change anything (retaining the same number of lines) and save changes
{( ⎕STOP⍵)( ⎕TRACE⍵) (⊣/⎕MONITOR⍵)}'foo'⍝ Windows IDE and Linux TTY correctly reports: 1 2 2 3 1 3⍝ Ride INCORRECTLY reports: 1 2
The text was updated successfully, but these errors were encountered:
xpqz
changed the title
TRACE and MONITOR bits not respected, only STOP
Support TRACE and MONITOR bits
Jun 8, 2023
(originaly reported by nic as mantis 0018408)
The RIDE protocol does now pass TRACE and MONITOR bits for edit/trace windows, whereas it only used to pass STOP bits though.
Editor deletes ⎕TRACE and ⎕MONITOR points when function was fixed with 2 ⎕FIX 'file://...' This happens only when using the RIDE protocol, and not when using the Windows IDE or the Linux TTY version.
Repro:
The text was updated successfully, but these errors were encountered: