Put temporary files in a temporary directory. about go-plus HOT 10 CLOSED

Yes, the flicker is indeed undesirable. We could look to redirect the output to a temp directory (http://nodejs.org/api/os.html#os_os_tmpdir) - do you want to make an attempt at it and make a PR?

from go-plus.

I just went ahead and fixed it - hope that's ok. Unfortunately this only redirects output for files which are not test files - saving a test file still causes a flicker in the tree, as I'm not sure you can redirect test output generated via the -c flag.

from go-plus.

Still an improvement! Is there anything else that I might help with? I looked at the gocode integration but found it difficult + the atom autocomplete UI is lacking

from go-plus.

Gocode integration is largely dependent on us making a PR against the core autocomplete package (which should find its way downstream to autocomplete-plus). Specifically, we need to introduce some events we can subscribe to that will permit us to step into the autocomplete pipeline and make suggestions.

from go-plus.

Issue for test output redirection: https://code.google.com/p/go/issues/detail?id=7724

from go-plus.

Proposed patch to go test to support test output redirection: https://codereview.appspot.com/85230043

from go-plus.

Looks like this will be fixed after go 1.4 is released: https://code.google.com/p/go/source/detail?r=ed23bbff73da

from go-plus.

Update: go 1.4 will ship with the changes required to prevent the test binary flicker: http://tip.golang.org/doc/go1.4#minor_library_changes

The go test subcommand has a new flag, -o, to set the name of the resulting binary, corresponding to the same flag in other subcommands. The non-functional -file flag has been removed.

from go-plus.

I'm going to preemptively support this so that when 1.4 drops it will just work 😄.

from go-plus.

golang/go@ce143f2 << this is now released in go 1.4 - I'd appreciate any feedback on whether this now suppresses the flicker in go 1.4, or if you still see it.

from go-plus.