Comments
3 comments
-
One other suggestion.
Have an option to only pop up the candidate list if there are no characters behind the cursor. For example, if I hit <tab> when the cursor is in front of a column name, I don't want the candidate list to pop up. I may rarely need to see the candidate list when doing this, but I would just use <ctrl+space> in these situations.
This is mainly a problem when restructuring poorly structured queries to make them more readable, and using <space> and <tab> both constantly pop the candidate list up.
I beleive this would make it more consistent w/ VS behavior.
Thanks. -
Certainly the candidate list (intellisense) topic is a hard one to implement, so what about this:
- You already have a delay time for the candidate list, what about abiding by it all the times, except when pressing ctrl+space (if applies); i.e. it doesn't matter if I just hit ",", wait for that delay.
- If I write exactly a snippet trigger and hit one of the completion keys expand the snippet, it doesn't matter if I was fast enough that the candidate list didn't show, I wouldn't need it anyway (there may be the need to define what completion keys apply for this "exact trigger match" thing, e.g. spacebar and tab may be exceptions).
Also, I would like to be able to define what "candidates group" I want by default (e.g. functions). Oh, and don't forget about the code indentation. -
Hi,I see you have a list of characters that complete (and close) a candidate list, but can we also have a similar list that triggers a candidate list?
For example, I would think characters like ")" should not bring up the candidate list. I'm thinking I ran across other characters that would seem appropriate to disable, but I can't think of them now.
But right now, it seems there are several (if not most) non-alphanumeric characters that trigger the candidate list, and I'm thinking I would turn most of these off. In fact, if I had the options available, I might have the tab key be the only key that triggers the candidate list. This would probably suite my coding style the best.
We are trying to improve the issue. For now it seems you would be best served by turning the auto-pop up off completely (via the options dialog) and use Ctrl + Space to pop it up manually.Also, the candidate list seems to be triggered even inside of a literal string. Management Studio is able to parse the query to determine what is inside literals (it turns it red), so hopefully this wouldn't be too hard.Have an option to only pop up the candidate list if there are no characters behind the cursor. For example, if I hit <tab> when the cursor is in front of a column name, I don't want the candidate list to pop up. I may rarely need to see the candidate list when doing this, but I would just use <ctrl+space> in these situations.This is mainly a problem when restructuring poorly structured queries to make them more readable, and using <space> and <tab> both constantly pop the candidate list up.You already have a delay time for the candidate list, what about abiding by it all the times, except when pressing ctrl+space (if applies); i.e. it doesn't matter if I just hit ",", wait for that delay.If I write exactly a snippet trigger and hit one of the completion keys expand the snippet, it doesn't matter if I was fast enough that the candidate list didn't show, I wouldn't need it anyway (there may be the need to define what completion keys apply for this "exact trigger match" thing, e.g. spacebar and tab may be exceptions).
We will try to do something like this, i'm afraid it wont be in the current version, though.
Regards,
Tilman
Add comment
Please sign in to leave a comment.
For example, I would think characters like ")" should not bring up the candidate list. I'm thinking I ran across other characters that would seem appropriate to disable, but I can't think of them now.
But right now, it seems there are several (if not most) non-alphanumeric characters that trigger the candidate list, and I'm thinking I would turn most of these off. In fact, if I had the options available, I might have the tab key be the only key that triggers the candidate list. This would probably suite my coding style the best.
Also, the candidate list seems to be triggered even inside of a literal string. Management Studio is able to parse the query to determine what is inside literals (it turns it red), so hopefully this wouldn't be too hard.