{"id":4198,"date":"2017-09-21T21:16:34","date_gmt":"2017-09-22T02:16:34","guid":{"rendered":"http:\/\/neosmart.net\/blog\/?p=4198"},"modified":"2017-09-21T21:22:25","modified_gmt":"2017-09-22T02:22:25","slug":"how-to-import-any-linux-command-into-your-windows-10-environment","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/how-to-import-any-linux-command-into-your-windows-10-environment\/","title":{"rendered":"How to import any Linux command into your Windows 10 environment"},"content":{"rendered":"

At NeoSmart Technologies, we’re\u00a0huge<\/em> fans of the new Windows Subsystem for Linux,1<\/a><\/sup> and have spent a lot of time trying to make the transition between the native Win32 subsystem and the Linux\/WSL subsystem as seamless as possible.<\/p>\n

For those of you that haven’t already seen it, we recommend reading our previous article\u00a0Meet $, your new best friend for WSL<\/a>\u00a0for an introduction to WSL and $<\/code>, our nifty helper utility that lets you directly run Linux commands in your Windows workflow. In brief, we developed $<\/code>\u00a0(also known – though less affectionately – as RunInBash<\/code>) to make it possible to run Linux utilities directly from within a Windows workflow, complete with arguments, stdin<\/code>,\u00a0stdout<\/code>, and\u00a0stderr<\/code>\u00a0redirection, and more.<\/p>\n

<\/p>\n

While $<\/code>\u00a0makes it dead simple to run any Linux command by prefixing it with — yup, you guessed it — $<\/code>, sometimes even that isn’t easy enough. For example, a lot of the developers at NeoSmart don’t use bash as their primary shell;2<\/a><\/sup> so having to run another shell, say fish<\/a>, by keying in <\/span><\/kbd>+R<\/span><\/kbd> then having to type in $ fish<\/code>, while still a distinct improvement over bash -c fish<\/code>, just didn’t cut it. And it’s not just a shell – there are a lot of “stand alone” command line utilities that developers rely on enough to launch directly without first entering a shell, such as ssh<\/code>\u00a0or nvim<\/code>.<\/p>\n

The ultimate solution we’ve landed on is a simple bash<\/del>\u00a0batch script that you can copy locally as many times as you like to launch any Linux tools you desire – without ever writing or changing a line of code<\/em>.<\/p>\n

Let’s jump straight into the batch file and then we’ll talk about how it works:<\/p>\n

@echo off\r\n\r\nset cmd=%~n0\r\n$ %cmd% %*\r\n<\/code><\/pre>\n
Disappointed? Why, were you expecting more? That’s really<\/em> all there is to it. The batch file above, when copied to a file called, let’s say, ssh.bat<\/code>\u00a0will run ssh<\/code>\u00a0under WSL, forwarding any arguments you pass to it along. All you have to do is put it in your PATH<\/code> somewhere!<\/p>\n
So how does it work? First, the batch file gets its own name via the %~n0<\/code>\u00a0magic syntax.3<\/a><\/sup> This gives us the file name without the directory component, so in this case, ssh<\/code> – which will be taken as the name of the command to run on the Linux side of things.<\/p>\n
The rest of the magic is all thanks to $<\/code>, which takes care of escaping arguments and passing them to bash.exe<\/code>\u00a0in such a way that you can keep your sanity instead of pulling out your hair trying to figure out how to double-escape an '<\/code>\u00a0in an argument enclosed in \"<\/code>\u00a0when your command contains spaces and you need to pass it in to bash -c<\/code>\u00a0enclosed in another… forget it. That’s what $<\/code>\u00a0is there for.<\/p>\n
Have another Linux tool you use often? Just copy your ssh.bat<\/code>\u00a0over to tool.bat<\/code>\u00a0and you’ll be on your merry way. If you want to get all fancy, you can even create a symlink instead, and then if you ever want to make some changes to this batch file (though hopefully you’ll never need to) you’ll only need to change one and the rest will automatically follow suit. It really couldn’t get any easier than this.<\/p>\n
If you don’t already have $<\/code>\u00a0installed, you can either download it here<\/a>\u00a0or install it with chocolatey via choco install RunInBash<\/code>.<\/p>\n
  1. Yes, we refuse to call it by its ungodly “Bash on Ubuntu on Windows” moniker ↩<\/a><\/p><\/li>
  2. And, honestly, who can blame them? Have you seen the syntax bash uses to access and escape elements of an array? ↩<\/a><\/p><\/li>
  3. Yes, batch is ugly… perhaps even uglier than bash. ↩<\/a><\/p><\/li><\/ol>","protected":false},"excerpt":{"rendered":"
    At NeoSmart Technologies, we’re\u00a0huge fans of the new Windows Subsystem for Linux,1 and have spent a lot of time trying to make the transition between the native Win32 subsystem and the Linux\/WSL subsystem as seamless as possible. For those of … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":505,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[568,5,965,887,950],"class_list":["post-4198","post","type-post","status-publish","format-standard","hentry","category-software","tag-bash","tag-linux","tag-runinbash","tag-windows-10","tag-wsl"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t