hirse / brackets-ungit Goto Github PK

Hello Hirse,
Firstly thank you for Ungit!

FYI
I just ran into the same issue as Originally posted by @terraconnect in #7 (comment)

• The Brackets extension installation is successful
• starting the "Toggle Ungit View" process brings no errors and yet stays idle...

Note that Ungit is working perfectly on the same system when started from:

• bash
• Visual Studio Code / Ungit extension

Not issue as much as FYI.

I had a problem installing this initially because the extension couldn't find my npm and node commands. The prompt shown indicated it was attempting a bash command. My default shell is zsh (ohmyzsh to be specific) so all my path config is there.

I did check that when switching to bash, the node and npm executables were found.

Following the tip for manually installing in #2, I was able to run the npm install from the shell and things seem to work ok now.

Running Brackets 1.4 on very latest Mac OS X 10.10.5. Installed npm and node are 1.4.28 and v0.10.40 respectively.

Hey Jan,

thanks for the neat extension idea. It already takes about 5 minutes to install. Is this normal?

Cheers,

Ole

I have tried to install ungit through Brackets Ungit but recieved message provided in title, then i installed ungit through terminal, all works fine if use 'ungit' command in terminal, but even after reinstalling extension i still recieving message from header while trying to open ungit from side panel

❯ npm -v
2.13.1
❯ which npm
/usr/local/bin/npm
❯ uname
Darwin
❯ /bin/sh npm
/usr/local/bin/npm: npm: line 2: syntax error near unexpected token ;' /usr/local/bin/npm: npm: line 2:;(function () { // wrapper in case we're in module_context mode'

Sadly the extension cannot be installed, yielding an error.

Hi Jan,

the finished is better now but maybe just close the window to show that it is installed? :/
Unfortunately there is a bug in your new version:
Uncaught ReferenceError: Promise is not defined main.js:61

It's not my cup tea, this view of Git, so I uninstall the extension... Turns out that doesn't work:

Nothing in the developer console is added. Just this error message.

This is on Brackets 1.4, Windows 7 x64, and (not sure if you need these) NPM 2.11.2 and Node 0.12.5.

This is cool!

Can I add this to Ungit's readme? Or would you like to send a PR to Ungit?

Enabling this extension causes very high CPU usage when Brackets is in the background. By that I mean above 4%, which may not sound like much, but when the extension is disabled, Brackets uses less than 1% CPU in the background.

I keep getting the above warning.

However, when I run the command, and my version is updated, the ungit extension seems to ignore it... OR the ungit extension is looking at some other installation?