--
You received this message because you are subscribed to the Google Groups "weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/726e92f2-012d-412a-91d2-bdba93ae1fd9n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/3b39341b-6d61-4339-b8f7-d9e6072273c4n%40googlegroups.com.
It really is a 'talking to humans' issue, not, in any real sense,
a bug in the code. weewx.conf is about the only place that a
(non-developer) human will be 'talking' to weewx, so it seems
reasonable to take a few extra steps to make the 'conversation'
there more natural for the human. I am still running V4.10, and
haven't really looked at V5.x, but if you would like to point me
to the code in V5 that scans and parses weewx.conf, I will take a
stab at it.
You received this message because you are subscribed to a topic in the Google Groups "weewx-development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-development/uaMCfsWGGxs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CAPq0zEDtqz5%3D5udtqCzXRi3bmybzgA58oRmhbKPTS5_mUdojiw%40mail.gmail.com.
-- Peter R. Fletcher <pe...@fletchers-uk.com> Home Page - https://pfletch.fletchers-uk.com