quote:

---

Originally posted by feline

Are you talking about using Find References on the current file only? Or something slightly different?

---

quote:

---

Originally posted by feline

For now have you considered simply running Find References and then telling it to stop? It should scan the current file first already

case=5180

---

quote:

---

Originally posted by feline

For now have you considered simply running Find References and then telling it to stop? It should scan the current file first already

---

quote:

---

Originally posted by sl@sh

quote:

---

Originally posted by feline

For now have you considered simply running Find References and then telling it to stop? It should scan the current file first already

---

I just tried this. Unfortunately, if you prematurely stop the find, then, apparently, the symbols already found are [u]not[/b] being highlighted! (hmm, I wonder if I'm being too excessive with commas here )

P.S.: an afterthought: would it be possible for VA to set some sort of mark into the sidebar (where the breakoint indicators go)? This would make it easier to spot symbols on very long lines (outside the view) or when the highlight color-to-background color contrast isn't too great.

---

quote:

---

Originally posted by feline

I got the impression from the last line of RoSe's post. Hanging out here trains you to try and read between the lines, but you don't always get this right

Scrolling... but that's what the page up / page down keys and next / previous context keys are for! Different people view things differently, but years working on a dumb terminal with VIM, to me scrolling always means moving the caret up / down the code. From this point of view picking up the symbol the caret is currently sitting in is likely to produce "interesting" effects most of the time.

---

quote:

---

Originally posted by feline

I had been picturing a command that you could bind to your own keyboard shortcut to highlight the current symbol, the one the caret is sitting in, just like Find References currently works.

Triggering on double click is an interesting idea, I am just wondering if there are any obvious edge cases where this will cause problems. *checks*

I had been thinking of how F8 works in MS Word, I am sure I have seen double click select a word, triple click to select a line, and so on, but the IDE is not doing this. Shows how much I use the mouse when coding

I have put a note about this on the feature request, case=5180

---

quote:

---

Originally posted by Sasa
No, no special command, double-click should be fine. This is how it works in eclipse and it works beatifully.

---

quote:

---

Originally posted by sl@sh

quote:

---

Originally posted by Sasa
No, no special command, double-click should be fine. This is how it works in eclipse and it works beatifully.

---

IIRC Eclipse does not require double-clicking.

I like the shortcut-to-command suggestion - you can always define left-double-click to be your shortcut if you so prefer

---

static void testFunction()
{
    int nFoo;
    nFoo++;
    nFoo--;
}

quote:

---

Originally posted by feline

I think I know the answer, but I will ask anyway. What happens if I do this:

static void testFunction()
{
    int nFoo;
    nFoo++;
    nFoo--;
}

and select the red bit? This is not going to work at all in the context of VA's Find References, since Find References should not even be offered on this.

I suspect we are back to the fundamental difference between Find References and the concept of "just highlight all piece of text that match the following regular expression pattern", which is what VIM will let you do, and is probably where this discussion is going

I have never used Eclipse, so I don't actually know what it is doing, so maybe I guessed wrong.

---

static void testFunction()
{
    int nFoo;
    int nFooBar;

    if(true)
    {
       int nFoo;
       nFoo++;
    }

    nFoo++;
    nFooBar++;
    nFoo--;
}

static void testFunction()
{
    int nFoo;
    int nFooBar;

    if(true)
    {
       int nFoo;
       nFoo++;
    }

    nFoo++;
    nFooBar++;
    nFoo--;
}

quote:

---

Originally posted by feline

Is this matching limited to the current function (code is parsed) or simply whole word and case matching?

The first is exactly what VA's Find References does, but some of the discussions here seem to be talking about simple string matching with no code parsing.

If you are only looking for a local variable then trigger VA's Find References, it is clever enough to know that you are searching for a local variable and you get a nearly instant result.

---

quote:

---

That's exactly it: Find References in current file only.

Since VAX parser already does a global Find References, doing it locally shouldn't be too much of a stretch I am guessing.

It would be an easy to implement, super feature to have that no other helper tools have.

Thanks.

P.S: If this task proves to be more challenging, a phased in approach could be used, where Phase1 will be simple string match, and Phase2 in next build could be the Find References in current file only.

---

quote:

---

Originally posted by feline

*nods* the open case that I found is asking for Find References, limited to the current file, which apart from marks in the sidebar is exactly what you are looking for.

The references to Eclipse are confusing me more than helping me, since I have never used it, so I have no good mental model of what people are referring to.

---

quote:

---

Originally posted by feline

*um*

Assume for a moment that I am working on a function that does not fit on the screen. I have various functions that do not fit, often for good reasons.

This means that I trigger this command on something inside this function, to see the references to the "thing" quickly and easily, and then when I try to find them the highlighting disappears...

Isn't this rather unhelpful?

---

quote:

---

Originally posted by feline

I think I finally understand now I have put a note on the case about this. It is almost a separate feature / command, but sitting on top of exactly the same Find References logic.

---