-
Notifications
You must be signed in to change notification settings - Fork 9
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
Not loading in Espresso 2.0.5? #3
Comments
Works for me. Can you open Console app and check if there are any errors when Espresso starts? |
Just the following: 7/12/12 9:15:43.997 PM Espresso[25187]: Not including optional grammar with root zone sourcecode.js |
So, how did you installed this plugin? Can you post a screenshot of of Espresso’s Sugars folder content? |
I tried it both ways - renaming and double clicking to install, and then when that didn't add anything to the Actions menu, I tried simply dragging the .sugar file to the correct folder. Screenshot coming... Worth noting, I just remembered having something similar happen the first time I tried to install Emmet on my mac Pro. Worked fine on my Air though. |
That’s strange... Everything looks fine. Can you type |
No it doesn't do anything unfortunately :( On 07/12/2012, at 10:14 PM, Sergey Chikuyonok notifications@github.com wrote:
|
The only way I can try to help you is if you give me access to your desktop. Can we do this via TeamVewer? |
Certainly, I could download that, or use iChat/Messages with screen sharing? On 09/12/2012, at 9:19 PM, Sergey Chikuyonok notifications@github.com wrote:
|
Yeah, let’s try with Messages. I never did so with Messages/iChat. I hope my GTalk account serge.che@gmail.com is enough? |
I'm online now Sergey, scottrichardson@mac.com is my iChat account :) Scott On 09/12/2012, at 11:27 PM, Sergey Chikuyonok notifications@github.com wrote:
|
I’ve updated README with better installation process description :) |
Hi there,
I just tried to install Emmet into Espresso 2.0.5 but nothing happened. It doesn't appear in the Actions menu. Is this a known issue?
Scott
The text was updated successfully, but these errors were encountered: