Update README with similar projects
DavidLGoldberg opened this issue · 6 comments
SublimeText has been missing this package for years so I implemented an equivalent a few weeks back: https://github.com/jgburet/jumpy-sublime
Today someone opened an issue and created a PR because the description I had so far wasn't really explicit (An equivalent of Atom's Jumpy package, for Sublime Text.) to change it into An equivalent of Atom's Jumpy package that creates dynamic hotkeys to jump around files and across visible panes, for Sublime Text.... just like yours.
jgburet/jumpy-sublime#2
I was wondering if you were okay @DavidLGoldberg to let me use this description as well for my ST package?
Feel free to use the description you think is best. Normalizing them would be great though!
Thanks for the reference / citation :)
I can't wait to get around to reading your code. Jumpy was actually originally intended for sublime, I had a really bad prototype.
The name actually comes from jum.py 😮 Sublime all still python?
FYI: I am inches away from releasing my version of jumpy (going to call it jumpy2 I think) to vs-code as the one there is a little lacking (I don't use it for example, because I use vim extension and it conflicts etc)
The version I have works fairly nicely so far, probably an MVP, but want to make it a little nicer before release. I'm sharing the elm state machine I made from the atom version! It's also typescript so that's nice.
Do you just use sublime or do you use vs-code now? All 3? I am mostly all vs-code now. A bit of vim on the terminal of course heh.
Maybe we can collab on stuff in the future? Reach out if you ever want to or questions!
Sublime all still python?
Yup, still.
I never really wrote anything in python before so there probably might be some really ugly stuff in my code. Comments are appreciated!
I'm sharing the elm state machine I made from the atom version!
That's neat!
I looked into it because I also thought having a state machine was the way to go but it wasn't necessary in ST.
Do you just use sublime or do you use vs-code now? All 3?
I moved to Atom in 2017 I think because it was pretty similar to ST and I couldn't get some ST packages to work in our monorepo (like, handling several different linter configs). I'm back to only ST since January :)
Maybe we can collab on stuff in the future? Reach out if you ever want to or questions!
I'd love that!
@jgburet Hey FYI, I referenced your sublime version on my new extension (for VS Code)
Give it a try if you ever use VS Code!!!
https://marketplace.visualstudio.com/items?itemName=DavidLGoldberg.jumpy2
I still have to get around to actually finishing this issue (adding your link to this version of Jumpy etc). I want to do a few things like that soon. Keep me in mind for any sort of collaboration! Just reach out!
Thanks a lot!
I looked at the video. It's really cool!
- How did you handle the back & forth? There's an API in VSC to register where your cursor has been moving? That's definitely something I've been missing. Gotta look if there's anything similar in ST.
- Also your documentation looks really professional.
Nice job! 👏
Sure will :)
For example, some functionalities I've been looking for were the ability to add more cursors, and create selections from a current position to a new one.
WDYT about these?
I really didn't have fun witth ST's API, I wish we could do more with it (and in JS 😆)!
Thanks! And thanks for watching! :)
Yes back/forward functionality built in. Not amazing with vim scrolling (hjkl) or non vim (arrow keys)...but works GREAT with Jumpy! (hah!) Also it handles different files really nicely...tabs/panes etc. Yeah, I don't remember it being a feature in ST2. Old visual studio had a decent version that would bind to the MS ergo 4K's back/forwad keys below space bar heh.
Docs, yeah definitely gave it some time. Probably too much!
I don't know how the multiple cursor stuff would work. Sounds interesting. I use those features sparingly, although I've seen some people who are pretty great with them. In part because I lean on Vim's '.' (repeat key) or if something is too repetitive I'm often doing something wrong or sloppy.
As per the selection thing, you know that works in the atom version right? It's sort of automatically, if you've selected, it just auto grows, it works in vim visual mode or regular selection too heh. But if I recall it did take some code to make it do that ;) I wasn't able to get that going on VS Code yet, tried for a bit but I'll have to give it another shot. I'll probably miss that feature soon enough now that I'm getting back into Jumpying, but figured it wasn't a show stopper / MVP kind of a feature.