Re: [go-nuts] Re: gofmt question

Good points and I'm obviously going to deal with it. :-) Its sorta like all those agreements we click off on when we install software we just purchased. As if we have any other option but to agree to whatever the demands. :-) I'm already getting past it, just frustrating in some respects.

Re: [go-nuts] Re: gofmt question

Another nice aspect of this is that formatting consistency is ecosystem-wide instead of company-wide. On Sat, Jul 1, 2017 at 9:43 AM Shawn Milochik wrote: > On Sat, Jul 1, 2017 at 11:40 AM, Glenn Hancock wrote: > >> Thanks for the responses. I guess

Re: [go-nuts] Re: gofmt question

On Sat, Jul 1, 2017 at 11:40 AM, Glenn Hancock wrote: > Thanks for the responses. I guess I'll just deal with it. While I can > understand the need to format code the same way, I would rather have my > company policies dictate this instead of the all knowing Google force upon

Re: [go-nuts] Re: gofmt question

Thanks for the responses. I guess I'll just deal with it. While I can understand the need to format code the same way, I would rather have my company policies dictate this instead of the all knowing Google force upon me what they think is proper. Guess we should get used to the new world

Re: [go-nuts] Re: gofmt question

Hi, If you add comments to preserve space, then other people who code with you might not be appreciative :> Have a look at git's hooks here: https://git-scm.com/book/gr/v2/Customizing-Git-Git-Hooks and use those to place your personal formatting code and run Go's formatter. If you use svn or

Re: [go-nuts] Re: gofmt question

Find a way to use comments for your ""big space" On Fri, Jun 30, 2017 at 8:12 PM wrote: > I have a few such bug bears, so, my trick is to 'fix' fmt's helpful > services when I check a file out, and only run fmt automatically when the > file is committed to the