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

Is Sublime Text 3 Support Planned? #25

Open
tmuka opened this issue Sep 6, 2013 · 12 comments
Open

Is Sublime Text 3 Support Planned? #25

tmuka opened this issue Sep 6, 2013 · 12 comments

Comments

@tmuka
Copy link

tmuka commented Sep 6, 2013

I tried using the current git version fo sublime_tortoise with sublime text 3, but am getting an error in the console.
File "C:\Users\me\AppData\Roaming\Sublime Text 3\Packages\sublime_tortoise\Tortoise.py", line 63
except (NotFoundError) as (exception):

I'm poking around a bit to see if it might be an easy port, but i'm new to ST plugins...

@westy
Copy link

westy commented Sep 18, 2013

I'd like to add my support here too!

I've tried a few of the other Mercurial plugins for ST3, but none seem to work for me (with an older mercurial version), and I can't upgrade our version of hg at this point.
I need the plugin to work with whatever tortoise I have installed, and that's this.

This is the last thing I need to move myself and the team to ST3.
Please update it when you get the time.

@atwright147
Copy link

Hey guys,

Sadly, @wbond doesn't seem to be maintaining this plugin these days. I have been curating pull requests and fixes people supply for his repo here: https://github.com/atwright147/sublime_tortoise (but this is not a ST3 compatible plugin).

However, @asfaltboy made a pull request to me to add ST3 compatibility, here: atwright147#1

I get the impression from his messages that this is a partial fix but it might help.

I won't be merging it into my branch as I want to stick to ST2 until ST3 is release properly.

Hope this helps.

PS. I am not a Python developer, so I cannot properly maintain this plugin... :(

@asfaltboy
Copy link

I'll try to make sure it's ST2 compatible, guys, please chime in on the linked pull request as to what you'd like to see next (such as a separate release on package control, things that won't work, etc..)

@wbond
Copy link
Owner

wbond commented Sep 19, 2013

If people are interested in helping maintain the package, I would be more than happy to add collaborators. Unfortunately I no longer really use Windows and never Tortoise, so I'm not in a position to really contribute a ton.

If someone ends up being the main contributor, we could then talk about moving the repo.

@asfaltboy
Copy link

@wbond: I am willing to take it on, since it's really not a lot of work, and it's mostly done already.

Please see the PR @ atwright147#1 for the changes. Would you like to move the package control to one of our forks or leave it here and pull the changes? In other words, where should the latest version be managed?

@asfaltboy
Copy link

@wbond any decision yet?

@01-Scripts
Copy link

@wbond : Can you consider to add someone as a contributer (maybe @asfaltboy ?) to get the long missing ST3 support so many people are waiting for?

@fyneworks
Copy link
Collaborator

Hey guys, I've ended up here whilst looking for a fix for the same @tmuka reported. I'd been playing around for a few days... starting with TortoiseSVN which I forked into TortoiseGIT. I've never worked with Python or ST plugins before, but it seemed straight forward enough. So, fast forward 24 hours and I've forked Will's Tortoise and made Tortoise3.

The bad news: I had to remove the context menus to get it to work, maybe somebody will be able to figure it out, but I sure couldn't.

The good news: it seems pretty solid (tested with SVN and GIT repos), I also added git push and also a shortcut to open a git bash window in the current working directory, which I often do.

TortoiseSVN and TortoiseGIT work perfectly fine with menus and all if you only need one of the other.... but I personally prefer to have a single plugin (call it OCD) so will be using (and maintaining) Tortoise3 from now on. Hope that helps anybody else who ends up here. Feedback welcome!

@kelvinlouis
Copy link

@fyneworks that's some great news. I'm in the midst of migrating to ST3. I'm interested to see what your project can accomplish. I'm not fluent in py, but I'm willing to contribute in any shape or form.

@tmuka
Copy link
Author

tmuka commented Apr 12, 2014

Sounds great, Fyneworks! I'll try it out Monday. I like the idea of svn and
git being unified too...

Thanks for sharing!
On Apr 12, 2014 8:24 AM, "Fyneworks" [email protected] wrote:

Hey guys, I've ended up here whilst looking for a fix for the same @tmukahttps://github.com/tmukareported. I'd been playing around for a few days... starting with
TortoiseSVN https://github.com/dexbol/sublime-TortoiseSVN which I
forked into TortoiseGIT https://github.com/fyneworks/sublime-TortoiseGIT.
I've never worked with Python or ST plugins before, but it seemed straight
forward enough. So, fast forward 24 hours and I've forked Will's Tortoise
and made Tortoise3 https://github.com/fyneworks/SublimeTortoise3.

The bad news: I had to remove the context menus to get it to work, maybe
somebody will be able to figure it out, but I sure couldn't.

The good news: it seems pretty solid (tested with SVN and GIT repos), I
also added git push and also a shortcut to open a git bash window in
the current working directory, which I often do.

TortoiseSVN https://github.com/dexbol/sublime-TortoiseSVN and
TortoiseGIT https://github.com/fyneworks/sublime-TortoiseGIT work
perfectly fine with menus and all if you only need one of the other.... but
I personally prefer to have a single plugin (call it OCD) so will be using
(and maintaining) Tortoise3https://github.com/fyneworks/SublimeTortoise3from now on. Hope that helps anybody else who ends up here. Feedback
welcome!

Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-40279075
.

@fyneworks
Copy link
Collaborator

@kelvinlouis neither am I. Literally just forked out some code last week and starting messing about with it, but it's great so many of us want to chip in :-)

@tmuka glad to hear it! Hopefully if this provides a good base to go forward we'll get the attention of a python ninja that will make it good enough for everyone (then we can submit it to Package Control perhaps?)

ps.: I personally like the plugin being entirely keyboard based. My context menus are full as they are. But keen to hear what you guys think. Let me know when you've tried it out

@tmuka
Copy link
Author

tmuka commented Apr 16, 2014

@fyneworks, it seems to work great, and does just everything i need! thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants