On Fri, 26 May 2017 08:08:08 -0400, "Ted Unangst" wrote: > Edgar Pettijohn wrote: > > This may not be the best way to handle this, but it was the first fix to > > come to mind. Not sure where to put this in the manual or if its even > > worth documenting. Thoughts? > > I think this is a better fix. the user shouldn't worry about such things. at > least until a better path forward is determined.
That does seem better. OK millert@ - todd
