-
Notifications
You must be signed in to change notification settings - Fork 96
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
Running make file on specific folder/file #174
Comments
Yes, you can set the current working directory in a custom atom-build file: {
"cmd": "make",
"cwd": "{FILE_ACTIVE_PATH}"
} Save this as |
Thanks for the quick reply! I'm getting an error though which says
I copied exactly what you put up there into the file. |
Can you paste the contents of your |
|
Sorry, but with the proper line breaks. |
There's no comma after |
ah of course! Thanks! Thanks again for your help |
I'm guessing the PATH is not set correctly when you open Atom. You probably have something in your |
I'm sorry, I don't quite understand what you mean when you say |
|
You're right! That worked, would you mind telling me how to fix the PATH issue? Thanks for all your help with this, I really do appreciate it. |
It's no problem. It depends on the operating system. On Unix/Linux, you can inspect the PATH variable by e.g. See this issue and this issue for solutions from people with similar problems. |
Ok, so I added a line in my .bash_profile which says As I understand it, that should add xelatex to the end of my path (and I think it did based on Anyways, now the build works! Thanks for your help. |
Hi,
In the specific folder that I'm working in, I have a make file that uses pandoc to convert a markdown file to pdf, docx, and html. However when I use the build command I think it attempts to convert the whole project and thus immediately runs into an error in trying to convert the Read Me file in the root of my project. Is there a way to specify the command so that it will only run the make file in the current folder I'm in?
Thanks!
The text was updated successfully, but these errors were encountered: