[go-nuts] i want to create a stream instead of socket connection? but i failed, Is this feasible?But the code didn't work. how about “”top” How to read results continuously

2019-03-30 Thread feihong' yu
package main import ( "fmt" "io" "os" "os/exec" "strings" "time" "github.com/kr/pty" ) func main() { c := exec.Command("/bin/bash", "-l") c.Env = append(os.Environ(), "TERM=xterm") tty, _ := pty.Start(c) s

[go-nuts] Re: Using the CX register on 386 and AMD64 in Go Assembly

2019-03-30 Thread keith . randall
Fixed memory location is a global variable. This only applies to 386, not amd64. This applies only to (SB) dereferences, not to any other (SP, FP, or standard register). The text doesn't really say it, but it applies to LEAL as well as loads and stores. On Saturday, March 30, 2019 at 2:40:28 PM

[go-nuts] Re: Go wasm - package js - Set() fails for certain attributes

2019-03-30 Thread whitehexagon via golang-nuts
I haven't done much client side javascript, but I'm used to seeing 'class' and 'onClick' as attributes on a div or button. Strange that no errors were generated anywhere, but anyway, both tips work perfectly, Thanks!! Peter On Saturday, 30 March 2019 20:28:56 UTC+1, Rusco wrote: > > If you t

[go-nuts] Using the CX register on 386 and AMD64 in Go Assembly

2019-03-30 Thread Neven Sajko
The official documentation on using the Go assembly [0] says this: > When using the compiler and assembler's -dynlink or -shared modes, any > load or store of a fixed memory location such as a global variable must > be assumed to overwrite CX. Therefore, to be safe for use with these > modes, asse

[go-nuts] Re: Go wasm - package js - Set() fails for certain attributes

2019-03-30 Thread Rusco
If you try out your code in Javascript you can spot your error, it would be something like: but.className = "somecssclass"; but.addEventListener("click", somefunction); so for syscall/js (untested) something like: var cb js.Callback cb = js.NewCallback(func(args []js.Value) { fmt.Println("Cli

[go-nuts] Re: The aggresiveness of Go module

2019-03-30 Thread Uli Kunitz
This is the behavior for GO111MODULE=on. What is strange that the behavior is different from GO111MODULE=auto outside the GOPATH. I suggest to raise GO issue for clarification. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from

Re: [go-nuts] Re: Vue-inspired library with Go+WebAssembly

2019-03-30 Thread Mike Schinkel
> But it would certainly be cool to have a solution that provides an > Electron-like shell around a Vugu application. I'll make an issue for it so > it's noted for later. Yes! Exactly. Would be very interested in that. > On Mar 30, 2019, at 12:16 AM, Brad wrote: > > Yeah, it's different.

[go-nuts] The aggresiveness of Go module

2019-03-30 Thread Shulhan
I have a temporary directory, lets call them "~/tmp/sandbox/go/src", to test Go behaviour here and there that sometimes I always forget. This time I want to know how the interface{} type works. I create directory "interface" then inside it I create "main.go" file. When running it with "go run ."

[go-nuts] Go wasm - package js - Set() fails for certain attributes

2019-03-30 Thread whitehexagon via golang-nuts
So I create a html button, and try to set some attributes, some work, some fail, is there a reason for this? but := doc.Call("createElement", "button") but.Set("id", bID) //works but.Set("innerHTML", "Don't Panic") //works but.Set("title", "mybuton") //works but.Set("class",