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

Go to definition issue and issue with autocomplete #260

Closed
felkar123 opened this issue Sep 27, 2016 · 6 comments
Closed

Go to definition issue and issue with autocomplete #260

felkar123 opened this issue Sep 27, 2016 · 6 comments

Comments

@felkar123
Copy link

Go to definition in a function to a local variable does not work. In longer functions, it is necessarily to have reference to local variables.

Autocomplete should offer a list of variables that are in structure, on the top of list after typing a period "."

There is also a strange coloring in a .h file. If you type a bracket in a definition, then the text that follows will color in to blue. In a syntax like this:

define definition value(250) // This comment and every thing that follow is colored in blue

@sean-mcmanus
Copy link
Collaborator

sean-mcmanus commented Sep 27, 2016

Thanks for reporting this.

  1. I'm reproing the "go to definition" issue with local variables. It doesn't appear to be a regression from 0.9.1. We'll investigate.
  2. I don't understand what bug you're reporting about the auto-complete, but in general we are working on make the auto-complete on-par with the VS behavior. Can you explain what behavior you're expecting?
  3. I'm not able to repro the colorization issue. It's possible other extensions are causing this or the repro needs more text.

@felkar123
Copy link
Author

felkar123 commented Sep 27, 2016

  1. Thank you, that would be nice
  2. It's not a bug, but it's about user experience and it helps to write the code faster. When you type an instance of a structure and then type the period or an arrow "->" for pointers, auto-complete should offer you just the variables that are declared in that structure.
    Please refer to eclipse CDT extension. It has everything that an extension for C/C++ language needs.
  3. I will look if it's a problem of other extensions

@sean-mcmanus
Copy link
Collaborator

sean-mcmanus commented Sep 27, 2016

Yes, our team is working on # 2.

@sean-mcmanus
Copy link
Collaborator

sean-mcmanus commented Sep 27, 2016

# 1 is also currently "by design" (we currently don't parse inside functions), but we're working on implementing the feature.

@bobbrow
Copy link
Member

bobbrow commented Apr 24, 2017

# 1 is being tracked by issue #255
# 2 is being tracked by issue #13
# 3, I believe, was an issue with the C++ colorization grammar which has since been fixed. Please let us know if you still see this with the latest version of VS Code and our extension. I do not see this issue.

I will be closing this issue since I think we're tracking everything that needs to be tracked. Thanks for your feedback.

@bobbrow bobbrow closed this as completed Apr 24, 2017
@sean-mcmanus
Copy link
Collaborator

@felkar123 0.19.0 implements Go to Declaration with local variables (and the autocomplete was implemented a while ago).

@github-actions github-actions bot locked and limited conversation to collaborators Oct 18, 2020
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

3 participants