Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support TRACE and MONITOR bits #963

Closed
xpqz opened this issue Jun 7, 2023 · 0 comments
Closed

Support TRACE and MONITOR bits #963

xpqz opened this issue Jun 7, 2023 · 0 comments

Comments

@xpqz
Copy link
Contributor

xpqz commented Jun 7, 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:

   (' res←foo arg' '⍝ this is foo' 'res←arg' 'res←''foo'' arg') ⎕NPUT '/tmp/foo.aplf' 1
      2 ⎕FIX 'file:///tmp/foo.aplf'
      {(1 2 ⎕STOP )(2 3 ⎕TRACE ) (1 3 ⎕MONITOR )}'foo'
 1 2 2 3 1 3
      {( ⎕STOP )( ⎕TRACE ) (/⎕MONITOR )}'foo'
 1 2 2 3 1 3
      ⎕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 
@xpqz xpqz changed the title TRACE and MONITOR bits not respected, only STOP Support TRACE and MONITOR bits Jun 8, 2023
@e9gille e9gille closed this as completed in 2ca7021 Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant