-
Notifications
You must be signed in to change notification settings - Fork 1.5k
No information about how to use init.coffee #26
Comments
I am happy to take a look at it during the weekend. I can at least start it :) |
Feel free to post any questions here as you work on that section. |
Note: there's a start of such a section, but it seems it's not finished and not included in the book (I'm guessing that happens when you use https://github.com/atom/docs/blob/master/book/03-hacking-atom/sections/xx-init-file.asc |
Yeah, this is a small part of what was in the old guides but I couldn't find a good point for it in the new docs. This is mostly because I couldn't find a great reason to use it - like a real example of what someone might put in there. I was thinking of putting it at the end of the chapter, using some of what we've learned to show what might go into a file like this. @Trudko or @russlescai could you share some of what you put in your |
I was thinking of adding a command to run a process. I assumed it was usually to add a command to add a trivial piece of code. in this case I was going to add a command to read the contents of the current editor or open the file in sql management studio. Not really reusable enough for a package, but scratches a particular itch. |
@schacon fair point. I already asked this questions my self here you can see some answers Share your init.coffee. Personally I use it for something which is specific to my workflow but too small for creating whole package. For example I've created small custom command which opens test fixtures for class . I might created package so others could use it, but it would require extra effort to generalize it for others too. |
If you search for
Some of them are old and would need to be updated, but we're not lacking for examples 😀 |
#65 brought back the section on init.coffee and added a more realistic example. |
I have been trying to use init.coffee, but couldn't find any information anywhere on how to use it.
This could be a useful addition to the flight manual.
The text was updated successfully, but these errors were encountered: