I raised https://github.com/golang/go/issues/36052 for discussion.
On Mon, 9 Dec 2019 at 10:29, Dan Kortschak wrote:
>
> Thanks.
>
> Yes, I always have GO111MODULE=on, hence the difference.
>
> On Mon, 2019-12-09 at 10:04 +, Paul Jolly wrote:
> > > When you're not in a module it returns
Thanks.
Yes, I always have GO111MODULE=on, hence the difference.
On Mon, 2019-12-09 at 10:04 +, Paul Jolly wrote:
> > When you're not in a module it returns /dev/null on linux. I don't
> > suppose this is platform independent?
>
> I have to say what you saw surprised me until Daniel MartÃ
> When you're not in a module it returns /dev/null on linux. I don't
> suppose this is platform independent?
I have to say what you saw surprised me until Daniel Martà and I did a
bit of experimentation.
It seems the value of GO111MODULE matters here. If you have
GO111MODULE=on then the result
On Mon, 09 Dec 2019 19:57:48 +1030
Dan Kortschak wrote:
> Thanks.
>
> When you're not in a module it returns /dev/null on linux. I don't
> suppose this is platform independent?
Hi,
This command:
go env GOMOD
returns 1 emty line,
i dont see any /dev/null ?
--
Jamil Djadala
--
You received
Thanks.
When you're not in a module it returns /dev/null on linux. I don't
suppose this is platform independent?
On Mon, 2019-12-09 at 06:52 +, Paul Jolly wrote:
> go env GOMOD - gives the path to the go.mod in use in module mode,
> and is
> empty otherwise (i.e. GOPATH mode)
>
> On Mon, 9
go env GOMOD - gives the path to the go.mod in use in module mode, and is
empty otherwise (i.e. GOPATH mode)
On Mon, 9 Dec 2019, 00:25 Dan Kortschak, wrote:
> Is there a way to query whether an invocation of the go command would
> be running in module mode?
>
> thanks
> Dan
>
> --
> You
Is there a way to query whether an invocation of the go command would
be running in module mode?
thanks
Dan
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
