Martijn de Munnik

I like that idea even better, but I can imagine that a breaking change is too much for now Some actual data from my vessel (`nc 192.168.1.151 10110 | grep...

Thanks! I will use this idea in my code as I was already aliasing the VTG (and other sentences) because I needed them to implement another interface. If you want...

Reason: I use expr mainly to parse Modbus data, typical expression I would like to use are: `273.15 + (registers[0]

Hi @aaditya-panik, Thank you for the suggestion, it fixed the tests.

I have https://facebook.github.io/watchman/ configured to convert the go coverage to lcov format using https://github.com/jandelgado/gcov2lcov ``` [ "trigger", ".", { "name": "coverage", "expression": [ "anyof", [ "match", "go-nmea.coverprofile", "wholename" ] ],...

I'm using https://github.com/jandelgado/gcov2lcov now which is fine. It would be nice if I can configure ginkgo to automatically invoke commands after testing so lcov get generated immediately after running the...

> I am planning on adding LCOV format support in v2. You can get Ginkgo to invoke commands after every test run already - check out `--afterSuiteHook`. Thanks! That works...

Any progress on this issue? ``` found packages native (proc.go) and your_operating_system_and_architecture_combination_is_not_supported_by_delve (support_sentinel.go) in /home/munnik/go/src/github.com/go-delve/delve/pkg/proc/native ``` with forcing the os to FreeBSD: ``` # github.com/go-delve/delve/pkg/proc/native go/src/github.com/go-delve/delve/pkg/proc/native/proc.go:28:23: undefined: osProcessDetails go/src/github.com/go-delve/delve/pkg/proc/native/proc.go:56:23: undefined:...

Running `export BOKEH_CDN_VERSION=3.0.3 && nix run` resolves the issue.

For me it is ok to have a global identifier in this case but I think the second options is a better one for the project.