Pragmatic Software

>We can override the nearest_area field of WWO with the wttr.in data, but the real question is that perhaps WWO returns the data for the nearest_area instead of the area...

@chubin The `nearest_area` field does appear to be now be populated with more-accurate values, for the most part. Previously, I was always getting city names that were one city away...

Noticed something weird. If I query for "Bronx" I get "Baychester, New York" with a Lat/Long of 40.86 and -73.84. If I query for "Bronx, New York" I get "West...

>You can query any other location, and check how it will be resolved, like this: > `$ curl wttr.in/~Bronx,New+York | grep ^Location:` This indeed does say "The Bronx, Bronx County,...

`queried_location` sounds great. Should I go ahead and close this issue and open a new issue for `queried_location` or do you want to keep this one open?

closes #110

I have a question. Would it have been appropriate to create a PR for a simple one-word typofix? It seems to me that you would think I was trying to...

Sure thing. PR #114 fixes the typo. My editor and git both complained about trailing whitespace on some lines, so I cleaned those up too.

I noticed this too. Some sequences are unusual. You can still type them by using the Unicode code point directly. It says "U+1D160" in your screenshot, so you'd type `...

You can also make alternative more convenient sequences by editing the .XCompose file. Hopefully WinCompose will have a sequence editor interface soon.