GNU Screen works but not that well (detatchment kills silently, doesn't keep things you had running, active). Under this bash-under- PowerShell even shebangs work to run Win-native Node.js apps (with the #!/usr/bin/env node shebang). Also if you exit the bash you are back in normal PowerShell, and 'ls' has been unaliased so it runs the Cygwin one. Exit this PowerShell session and then launch a new one, you should end up in "PowerBash" assuming you've got your Cygwin path set up correctly. Put this in there: Remove-Item alias:\lsĪgain the ampersand is important and intended. This is your PowerShell profile script, make the directory tree (probably won't exist) and then notepad the file, creating it. Jack this in at your PowerShell prompt: Get-Variable PROFILE This sets the ability to run your profile script which we create next. #If you have an "Administrator" level user account Set-ExecutionPolicy RemoteSigned -Force #For Windows Vista, Windows 7, Windows 8 (does PowerShell even work on Windows XP?) This is for an 圆4 PowerShell so if you have 32-bit you probably don't need the second line (it sets the policy for both 64 and 32, when on 圆4). In a PowerShell shell (redundant?) execute these commands to open up the execution policy so it will run local scripts, including the 'autoexec' style one we're about to make, now called a 'profile script'. These will allow you to use Cygwin binaries from normal PowerShell, or to run bash and then have almost full Cygwin powers, all within your WebStorm terminal. #User PATH env var C:\cygwin\bin C:\cygwin\usr\bin C:\cygwin\sbin C:\cygwin\usr\sbin %ProgramFiles(x86)%\nodejs %USERPROFILE%\AppData\Roaming\npmĪdjust these to match your versions and/or strip out the AMD/ Nvidia/ Quicktime junk if you want, these were just my PATHs once I finished reordering and cleaning them up. #System PATH env var %SystemRoot%\command %SystemRoot%\system32 %SystemRoot% %SystemRoot%\System32\Wbem %SystemRoot%\System32\WindowsPowerShell\v1.0 C:\Python27 %ProgramFiles(x86)%\GTK2-Runtime\lib %ProgramW6432%\Microsoft SQL Server\110\Tools\Binn %ProgramFiles(x86)%\ATI Technologies\ATI.ACE\Core-Static %ProgramFiles(x86)%\AMD APP\bin\x86 %ProgramFiles(x86)%\AMD APP\bin\x86_64 %ProgramFiles(x86)%\NVIDIA Corporation\PhysX\Common %ProgramFiles(x86)%\Common Files\Microsoft Shared\Windows Live %ProgramFiles(x86)%\Windows Live\Shared %ProgramFiles(x86)%\QuickTime\QTSystem Set your paths similar to these, in your System properties: Note that bash set up as your Terminal Settings in WebStorm will not directly work due to some incompatibilities (the executable used in Terminal Settings must support Windows Console API, and Cygwin does not). You must have git and ssh and friends all installed and configured on Cygwin and WebStorm seems to work fine without native Git installed at all. By extension, this also fixes the bad Ctrl-C handling in PowerShell and other issues (like learning a brand new shell for no reason). Gtk (because the Cygwin version generally never plays well with Native apps also involved)įurther, it will set up PowerShell to launch with a more Cygwin-like environment ( bash and all).Python (because some of the Node.js/ npm things don't play well with Cygwin Python).Node.js (because there is no Cygwin version currently).This will set up WebStorm to use Cygwin versions of everything except for: If you already use Cygwin and its git and have openssh keys all set up for Github and etc, this is a way to keep one set of configurations, and a familiar shell. But, that would sort of negate most of the gains herein. Otherwise, you must NOT set up git in Cygwin so that the Native Git is found. You may skip the Git parts of that guide, and instead install Cygwin and the git and openssh it contains. Cygwin32, and WebStorm and Node.js etc all set up 32-bit. NOTE: This is all with 32-bit stuff even on 圆4 platform. Begin with the guide by here for general installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |