-
Notifications
You must be signed in to change notification settings - Fork 450
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
Improve usage and support #17
Conversation
@donaldpipowitch I think I may leave the Specs and Travis CI for later. |
Applied in order of precedence: - Default - User Home .jsbeautifyrc - Closest .jsbeautify to the current file, see #15
@donaldpipowitch I am done now. For those who wish to use this before it is published to Atom's packages: In your Terminal, change into a safe directory for cloning the repo and then run: # Clone fork repo
git clone git@github.com:Glavin001/atom-beautify.git
# Change into repo directory
cd atom-beautify/
# Install dependencies
npm install
# Uninstall old atom-beautify, if applicable
apm uninstall atom-beautify
# Link and use this atom-beautify
apm link /cc @Frozenfire92 |
Wow, this looks awesome! I'll be in my honeymoon in the next two weeks, so I can't look into the pull request in detail before merging. @karolyi Could you make a short review for this pull request and merge it into the master afterwards? Just if you have some spare time. Else I would do it after 2 weeks. Thank you both very much! |
Thanks, @donaldpipowitch! No worries. In the meantime, everyone can use the script I commented above. 😉 😉 for @Frozenfire92 @karolyi, let me know if there's anything else I can do. @donaldpipowitch, congratulations and have an amazing honeymoon!! |
|
Thanks for updating thank, @Frozenfire92 . I noticed I forgot the |
@karolyi I updated my PR, fixing those lines you commented on. Thanks. |
Thx, currently reviewing ... :) Stay tuned. |
All cool, merging 👍 |
Thank you, @karolyi ! |
Specs and Travis CI config, Specs (and Travis CI) #18