Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-04-23 Thread Elvis Stansvik
2016-04-03 21:00 GMT+02:00 Elvis Stansvik : > 2016-04-03 20:17 GMT+02:00 Feng Xiao : >> Hi Elvis, >> >> I think preserving comments at the very top of the .proto file is something >> the protocol compiler should do. I remember this feature was requested >>

Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-04-03 Thread Elvis Stansvik
2016-04-03 20:17 GMT+02:00 Feng Xiao : > Hi Elvis, > > I think preserving comments at the very top of the .proto file is something > the protocol compiler should do. I remember this feature was requested > inside Google as well and was implemented some time ago. Not sure if

Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-04-03 Thread 'Feng Xiao' via Protocol Buffers
Hi Elvis, I think preserving comments at the very top of the .proto file is something the protocol compiler should do. I remember this feature was requested inside Google as well and was implemented some time ago. Not sure if it's ported to the opensource repo though. If that's what you need,

Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-04-03 Thread Elvis Stansvik
2016-04-01 7:50 GMT+02:00 Elvis Stansvik : > Hi Feng, > > 2016-03-31 22:28 GMT+02:00 Feng Xiao : >> >> >> On Wed, Mar 30, 2016 at 9:40 AM, Elvis Stansvik wrote: >>> >>> On Wednesday, March 30, 2016 at 2:12:46 AM UTC+2, Horst Noreick

Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-03-31 Thread Elvis Stansvik
Hi Feng, 2016-03-31 22:28 GMT+02:00 Feng Xiao : > > > On Wed, Mar 30, 2016 at 9:40 AM, Elvis Stansvik wrote: >> >> On Wednesday, March 30, 2016 at 2:12:46 AM UTC+2, Horst Noreick wrote: >>> >>> the compiler uses GOPATH from environment >> >> >> Hm, I

Re: [protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-03-31 Thread 'Feng Xiao' via Protocol Buffers
On Wed, Mar 30, 2016 at 9:40 AM, Elvis Stansvik wrote: > On Wednesday, March 30, 2016 at 2:12:46 AM UTC+2, Horst Noreick wrote: >> >> the compiler uses GOPATH from environment >> > > Hm, I think you may have misunderstood me. GOPATH seems to be some > variable to control the

[protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-03-30 Thread Horst Noreick
> > Hm, I think you may have misunderstood me. GOPATH seems to be some > variable to control the paths searched by the Go language compiler > > Yes, it's true. I was in golang context, I looked in the source at github. Im not familar with this but i think that rel paths from the file

[protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-03-30 Thread Elvis Stansvik
On Wednesday, March 30, 2016 at 2:12:46 AM UTC+2, Horst Noreick wrote: > > the compiler uses GOPATH from environment > Hm, I think you may have misunderstood me. GOPATH seems to be some variable to control the paths searched by the Go language compiler. What I'm looking for is a way to

[protobuf] Re: Getting the full (on disk) path to an input .proto from plugin

2016-03-29 Thread Horst Noreick
the compiler uses GOPATH from environment -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send