gbin/screencastinator: scriptedit/ansi.go; 6 LoC

Found a possible issue in [gbin/screencastinator](https://www.github.com/gbin/screencastinator) at [scriptedit/ansi.go](https://github.com/gbin/screencastinator/blob/d428aa5b48da292c7d7258087356bac471a7b688/scriptedit/ansi.go#L154-L159)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to code was used in a composite literal at line 156

[Click here to see the code in its original context.](https://github.com/gbin/screencastinator/blob/d428aa5b48da292c7d7258087356bac471a7b688/scriptedit/ansi.go#L154-L159)

Click here to show the 6 line(s) of Go which triggered the analyzer.

```go
for _, code := range ALL_G0 {
if code.Code == b {
result = append(result, AnsiCmd{0, &code, ""})
break
}
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: d428aa5b48da292c7d7258087356bac471a7b688

Read scriptedit/ansi.go around lines 154-159 at commit d428aa5b48da292c7d7258087356bac471a7b688, then inspect the definitions of ALL_G0 and AnsiCmd. Determine whether the reported range-loop reference is a bug, mitigated, or desirable behavior, and leave the corresponding reaction on the issue.

Written by the indexing model from the issue text.