-
-
Save typeoneerror/1596565 to your computer and use it in GitHub Desktop.
{ | |
"cmd" : ["$file"], | |
"selector" : "source.shell", | |
"shell" : "bash" | |
} |
Thank you Andrew, that worked perfectly.
+1
I run a sh file using above build script and run smoothly but waits at some point and doesn't take input if I type.
rm: remove write-protected regular file `/etc/udev/rules.d/70-persistent-net.rules'?
I typed y but didn't take any action.
Any Idea?
In sublime text 3, I am using the following:
{
"cmd" : ["$file"],
"selector" : "source.shell",
"path" : "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"
}
Note: I had to add "path" above, as the terminal in Sublime was using a different PATH, my other attempts at adjusting my PATH were unsuccessful. Also see the build system reference for more details.
I also had to add the line as suggested above,
"path" : "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"
Even though I already set up my symbolic links in terminal properly = Yes, I can run "python3" from any location...
To hammer it in farther... When I type
"echo $PATH"
it returns
"/Library/Frameworks/Python.framework/Versions/3.4/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/Users/Hendrix/bin"
Yes, I am new at development. However, from logical deduction I ponder if sublime text 3 is not using ~/.bash_profile, or the system paths(??did I say that right?) as we might be drawn to assume... Then again... I am still at noob level, ,, but ya, adding the "path" line as suggested by 'farinspace' did the trick for me - OS X 10.9.5
Hi All, I new on sublime. How to add that code into sublime?
Edit:
Okay, tools, build system, new build system.. and replace all content to andrewheiss's code. Thanks.
thanks
For some language (for example russian) whitespace symbols can be found in path:
/home/username/Рабочий стол/test.sh
and "cmd" : ["$file"],
not works correctly. I recommend add quotes and chmod for set permissions
"cmd" : ["chmod +x \"$file\" && \"$file\"" ],
If one wants to also have a "debug mode", a simple variant is
{
"cmd": ["bash", "$file"],
"selector": "source.shell",
"variants":
[
{
"name": "Debug",
"shell_cmd": "/bin/bash -xv \"${file}\""
}
]
}
note the escaped quotation marks to avoid issues with spaces etc. in the file name
However, it seems like you can fix that by modifying the build system slightly. Instead of specifying "shell": "bash", you can manually pipe it through bash, like so: