Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Feature: Interactive buffers #9

Open
3 of 6 tasks
critiqjo opened this issue Sep 5, 2015 · 3 comments
Open
3 of 6 tasks

Feature: Interactive buffers #9

critiqjo opened this issue Sep 5, 2015 · 3 comments

Comments

@critiqjo
Copy link
Collaborator

critiqjo commented Sep 5, 2015

Ability to

  • From the breakpoints buffer
    • Delete breakpoints
    • Enable/disable breakpoint locations
    • Jump to breakpoint locations (useful?)
  • Select thread and frame from the backtrace buffer
  • Select thread from the threads buffer
  • Set watchpoints on local variables from the locals buffer
@critiqjo
Copy link
Collaborator Author

critiqjo commented Sep 14, 2015

Strategy:

  • Define syntax for each type of buffers
  • Use syntax element identifiers to make things interactive (ref)

@critiqjo critiqjo added this to the v1.0 milestone Dec 2, 2015
@critiqjo critiqjo added the easy label Apr 21, 2016
@ckwang
Copy link
Contributor

ckwang commented Jun 8, 2016

I'm interested in this feature too. If this is still in the roadmap of the plugin, I would be happy to implement it. :)

@critiqjo
Copy link
Collaborator Author

critiqjo commented Jun 8, 2016

And I would be happy to guide if you need any help. Skip the watchpoints part for now (but if you're super experienced with LLDB, go ahead).

The idea I had was to check if the following:

synIDattr(synID(line("."), col("."), 1), "name")

returns one of the names we are looking for (defined in the syntax file), to quickly assert that we are in the right line. Then use regex to extract the appropriate "number" (breakpoint, thread, frame ...) out. But if the former check does not simplify the latter regex, the former check may be skipped.

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

No branches or pull requests

2 participants