weatherrc(5)

πŸ“¦
version 2.5.0 Β· 2 versions
, in debian trixie, nixos 26.05, nixpkgs unstable, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– weatherrc β€” the config file for weather(1) πŸ’–

ok so bestie, you're reading the weatherrc(5) page from the File Formats Manual, and honestly? this little file is the moment. ✨


🌸 NAME 🌸

weatherrc β€” the configuration file format for the weather(1) utility. yes, that weather. the one you keep running. she has a config file and she's thriving.


πŸŽ€ DESCRIPTION πŸŽ€

So the whole vibe of the weatherrc file format is: you're defining a set of aliases that group together URIs for METAR station conditions and alert/forecast zones. but that's not all, bestie β€” other command-line options and flags for the weather utility can be specified too. it's giving "one file to rule them all" πŸ’…

The file is organized as an INI-format config. alias name goes in [] brackets, and the associated parameter/value pairs go on the lines right after it. Parameters and their values are separated by = or : characters. and here's the iconic part β€” multi-word values do not need quoting. no quotes, no stress, we love a low-maintenance queen 🫢

These parameters are supported...

  • alert β€” include local alert notices. possible values are False and True or 0 and 1.
  • atypes β€” list of alert notification types to display. ex: tornado,urgent_weather_message.
  • cache β€” control all caching. possible values are False and True or 0 and 1.
  • cache_data β€” control retrieved data caching. possible values are False and True or 0 and 1.
  • cache_search β€” control search result caching. possible values are False and True or 0 and 1.
  • cacheage β€” duration in seconds to refresh cached data. ex: 900.
  • cachedir β€” directory for storing cached searches and data. ex: ~/.weather.
  • conditions β€” output current conditions. possible values are False and True or 0 and 1.
  • defargs β€” list of default command-line arguments. ex: avl,rdu.
  • forecast β€” include a local forecast. possible values are False and True or 0 and 1.
  • headers β€” list of conditions headers to display. ex: temperature,wind.
  • imperial β€” filter/convert conditions for US/UK units. possible values are False and True or 0 and 1.
  • metric β€” filter/convert conditions for metric units. possible values are False and True or 0 and 1.
  • quiet β€” skip preambles and don't indent. possible values are False and True or 0 and 1.
  • setpath β€” directory search path for correlation sets. ex: .:~/.weather.
  • verbose β€” show full decoded feeds. possible values are False and True or 0 and 1.

✨ EXAMPLES ✨

ok so here's the tea β€” the following is an example ~/.weather/weatherrc defining a couple aliases named home and work, to be displayed when running the utility with no aliases specified...

[default]
defargs = home,work

[home]
description = Conditions and Forecast at Home
forecast = True
metar = http://tgftp.nws.noaa.gov/data/observations/metar/decoded/KRDU.TXT
zone_forecast = http://tgftp.nws.noaa.gov/data/forecasts/zone/nc/ncz041.txt

[work]
description = Conditions at Work
metar = http://tgftp.nws.noaa.gov/data/observations/metar/decoded/KGSO.TXT

Now if weather is invoked by itself on the command line, it will output conditions for home and work, and also a forecast for home only. no cap. it just does that. πŸ¦‹


πŸ‘‘ AUTHOR πŸ‘‘

Specification and manual written by Jeremy Stanley <fungi@yuggoth.org>. shoutout to the author, fr fr. 🫢


🌈 SEE ALSO 🌈


and that's the whole page, bestie!! this was version 2.5.0, dated 2024-05-11, and honestly? iconic. go configure something. mwah πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from