From playing with it a little, 1) I dig it and not unlikely I'll use it in some situations I'd otherwise hit the Playground for, 2) here, of course, are some ideas:
- Running bradfitz/goimports (if it's in the $PATH) on the session file before executing it and picking up any imports it adds. So f, err := os.Open("foo") would work without me explicitly :import'ing os.
- Enabling gocode autocompletion after you type :doc, and possibly stripping a trailing '('. This'd be a cheat to let you type :doc fmt.P[tab] enter.
- Hiding __gore_p from the written/printed output. Possible there's a technical reason that's less of a good idea than it sounds like.
- :read to load a session, and/or similar shortcuts to save you from retyping the same inputs to set up the environment -- e.g., taking a session filename on the command line and defaulting to ~/.gorerc if it exists.
- :play -- submit some version of the session file to the Go Playground and print the URL (for sharing, say). The Playground's "About" link says automatic use is OK if you're cool about it (and has a more complete definition of "if you're cool about it").
Thanks for the work and don't let the spew of ideas distract from that I like what you've got and find it useful.
Also, I feel sort of annoyed at myself for even having replied like that to a useful tool. :P Forget all that I wrote up there, and good work, author, should you ever read this.
- Running bradfitz/goimports (if it's in the $PATH) on the session file before executing it and picking up any imports it adds. So f, err := os.Open("foo") would work without me explicitly :import'ing os.
- Enabling gocode autocompletion after you type :doc, and possibly stripping a trailing '('. This'd be a cheat to let you type :doc fmt.P[tab] enter.
- Hiding __gore_p from the written/printed output. Possible there's a technical reason that's less of a good idea than it sounds like.
- :read to load a session, and/or similar shortcuts to save you from retyping the same inputs to set up the environment -- e.g., taking a session filename on the command line and defaulting to ~/.gorerc if it exists.
- :play -- submit some version of the session file to the Go Playground and print the URL (for sharing, say). The Playground's "About" link says automatic use is OK if you're cool about it (and has a more complete definition of "if you're cool about it").
Thanks for the work and don't let the spew of ideas distract from that I like what you've got and find it useful.