From b5f5e9743827d9f07dc130a4b844313cd0b503cb Mon Sep 17 00:00:00 2001 From: "Stephen McQuay (smcquay)" Date: Mon, 18 Sep 2017 09:26:34 -0700 Subject: [PATCH] formatting --- readme.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index b1d94f9..0b79d9a 100644 --- a/readme.md +++ b/readme.md @@ -2,6 +2,11 @@ Have you ever peered into `$GOPATH/bin` only to wonder where all that stuff came from? -As someone who originally came from scripting languages where one could trivially peer into an 'executable' using an editor, the origin of binaries in that folder (specifically if `GOPATH=~`) was completely opaque to me. Not any more! +As someone who originally came from scripting languages where one could +trivially peer into an 'executable' using an editor, the origin of binaries in +that folder (specifically if `GOPATH=~`) was completely opaque to me. Not any +more! -`gorigin` helps shed light on this by creating a list of binaries in all the `bin` folders in the `GOPATH` and marching through all the `src` folders in the `GOPATH` and reporting when a go package with a package name of `main` matches. +`gorigin` helps shed light on this by creating a list of binaries in all the +`bin` folders in the `GOPATH` and marching through all the `src` folders in the +`GOPATH` and reporting when a go package with a package name of `main` matches.