Joey Parrish 177e80b9a7 No "beep" character on linter failures ...

By default, the linter produces a "beep" character (ASCII 7) on
failure.  This caused an extra character to appear in the buildbot's
log on the beginning of a line that should have served as a delimiter
to make parsing easier.  The beep therefore caused a parse failure in
the buildbot when it was proofing pull-requests with linter errors.

(For an example of this failure, see PR #144.)

The solution is the linter's --nobeep flag.

Change-Id: I1a0ea7529134f9556a849fd0dd6ccb70832e6a38

2015-08-17 13:16:08 -07:00

..

all.sh

Shaka Player release v1.0

2014-12-19 14:26:19 -08:00

audit_todo.sh

Create custom player controls.

2015-03-10 19:40:57 +00:00

build.sh

Added build options to disable unneeded features

2015-08-14 15:58:00 -07:00

checkversion.sh

Add a script to check versions.

2015-03-11 16:19:06 -07:00

docs.sh

Shaka Player release v1.0

2014-12-19 14:26:19 -08:00

gendeps.sh

Shaka Player release v1.0

2014-12-19 14:26:19 -08:00

lib.sh

No "beep" character on linter failures

2015-08-17 13:16:08 -07:00

lint.sh

Create custom player controls.

2015-03-10 19:40:57 +00:00

wrapper.template.js

Refactor compilation wrappers.

2015-04-10 12:38:07 -07:00