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

Fix instr/endin and opcode/endop detection #2

Closed
kunstmusik opened this issue Oct 18, 2019 · 1 comment
Closed

Fix instr/endin and opcode/endop detection #2

kunstmusik opened this issue Oct 18, 2019 · 1 comment

Comments

@kunstmusik
Copy link
Owner

Pete Goodeve reported that instr/endin and opcode/endop detection doesn't work if the keywords are indented in. Makes sense due to regex used in code.

  1. Fix the detection of instr/endin and opcode/endop
  2. Update the code to work even if cursor is on the lines with instr/endin/opcode/endop
@PeteCA
Copy link

PeteCA commented Oct 18, 2019

This must be some weird bug in vim. I played around and found that, for instance, just doing "/^\s*endin"/ from within an instrument works just as it should, but
':let end = search("^\s*endin")' fails!
OTOH something like ':let end = search("\s*endin")' succeeds (though not useful...).

What also works is ':let end = search("^[ \t]*endin")', so I guess that would be a workaround. I've changed the plugin on my machine appropriately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants