build

Description of the feature request:

For better bash-less Windows support,ctx.actions.run_shell could add command_bat (with the same behavior as genrule's cmd_bat) and command_ps (with the same behavior as genrule's cmd_ps).

This would, in particular, considerably simplify skylib's Windows support, where currently we are forced to write and execute temporary .bat files on Wind

Request to create a syntax highlight package for Atom IDE https://atom.io/

Related to #1203 #359

source: https://insights.stackoverflow.com/survey/2021#most-popular-technologies-new-collab-tools

I'd expect this to embed C:\temp\1.txt into the binlog, but it doesn't:

<Project>

  <Target Name="Build">
    <MSBuild Projects="$(MSBuildThisFileFullPath)" Targets="GetItems">
      <Output TaskParameter="TargetOutputs" ItemName="EmbedInBinlog" />
    </MSBuild>
  </Target>

  <Target Name="GetItems" Returns="@(ResultItem)">
    <ItemGroup>
      <ResultItem Include="C:\temp\

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Some of the repos that we import has ".go" in the file path. eg. https://github.com/nats-io/nats.go.

When using packr v2 to build packr parses the folder path as a file and reports error ".../nats.go" is a directory.

The issue is in findAllGoFiles in jam/parser/finder.go

I am happy to raise a PR if you like

A user tried setting script="dagster arg1 arg2 --arg3" on a pex_binary target, and was confused by a Pex error that the script could not be found.

My understanding of script and Python entry points is that they cannot have a space in the name like that. But we should find the PEP/specs specifying how entry points work and make sure we comply with the grammar. False positives would be a wo

What version of Garble and Go are you using?

$ garble version
v0.4.1-0.20210929123233-e7320ec9c034
$ go version
go version go1.17.2 linux/amd64

What environment are you running Garble on?

Dune systematically buffers the output of commands so that their output is not mixed up during parallel builds. However, this is not ideal for interactive commands that require direct access to the terminal.

Currently, the only workaround is to run dune with -j 1 --no-buffer which is not ideal since it completely disables parallelism and also require a specific dune invocation.

Another ide