Jump to any clickable element with jumpy?

Closing this since it is probably not of interest to you.

[DavidLGoldberg]

Absolutely is. Actually, my first thoughts about Jumpy was really a clickable region idea. I had the idea 10 or 11 years ago. This was a college project when I barely knew how to program, but the picture gives the idea:
http://uix.sourceforge.net/

The chrome extension vimium does a good job at this.

[DavidLGoldberg]

Did you ever raise the issue in Atom/atom? If so could you link me to it?

[tofagerl]

So if I understand this and a few other bugs correctly, there is no way to just use regex in order to put labels everywhere people want. I assume AST is the best alternative, but with AST camelcase and other mid-expression targets would be more difficult.

What about using regex within AST nodes?

[DavidLGoldberg]

Basically the discussions concluded in just hard coding the few edge cases
we all wanted.

On Wed, Jul 22, 2015, 06:26 Tom Fagerland notifications@github.com wrote:

So if I understand this and a few other bugs correctly, there is no way to
just use regex in order to put labels everywhere people want. I assume AST
is the best alternative, but with AST camelcase and other mid-expression
targets would be more difficult.

What about using regex within AST nodes?

—
Reply to this email directly or view it on GitHub
#70 (comment)
.

[tofagerl]

Well, that would be faster. Where can I find this discussion. And is there a gist somewhere where I can find a way to add newlines? I can probably hack it together myself, but... DRY...

[RAbraham]

Hi, first of all, thanks for making this amazing package.
I was wondering if this idea was still of interest to you. I would love to use jumpy to access links in the Symbol References View. For e.g., below, after I find all the references to a function, it would be great to use jumpy

• to be able to directly go to Line 46 of features/build_features.py which is another file.
• If I click on the bottom facing arrow to the left of features/build_features.py, it toggles and hides the code. It would be cool to do that with jumpy

[DavidLGoldberg]

Thanks! Any clickable element is maybe a little of a misnomer...check out some of the new code if interested...I now use a provider (ish) pattern for "labelers". So now, you can construct your own! For example I have one labeler for words and one for tabs. I have a version of jumpy coming soon which uses elm for the state machine parts...but the existing labeker pattern is left untouched. After that release the next was to get a tree view labeler released which was already spiked in one of the PRs. I just haven't gotten around to it. I could imagine accepting PRs for labelers quite often ...since they really shouldn't break the rest of jumpy...

…

On Sun, Jan 14, 2018, 1:09 AM Rajiv Abraham ***@***.***> wrote: Hi, first of all, thanks for making this amazing package. I was wondering if this idea was still of interest to you. I would love to use jumpy to access links in the Symbol References View. For e.g., below, after I find all the references to a function, it would be great to use jumpy - to be able to directly go to Line 46 of features/build_features.py which is another file. - If I click on the bottom facing arrow to the left of features/build_features.py, it toggles and hides the code. It would be cool to do that with jumpy [image: screen shot 2018-01-14 at 12 03 46 am] <https://user-images.githubusercontent.com/214189/34912997-83b0e19e-f8be-11e7-9aef-b5057eaea8a4.png> — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#70 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjTr6ATFmZU8tgmhpcsKF2Vvo5fYRuYks5tKYwbgaJpZM4FW6h7> .