wttr.in VS tmux-copycat

#!/bin/bash # Get weather information for a specified location LOCATION="London" curl "http://wttr.in/$LOCATION?format=3"

We’re going to use a free weather API, wttr.in, which gives us weather info just by calling a URL.

locals { url = format("https://wttr.in/%v?%v&format=%v&lang=%v&u=%v", urlencode(var.location), urlencode(var.options), urlencode(var.format), urlencode(var.lang), urlencode(var.units), ) } data "http" "weather" { url = local.url request_headers = { User-Agent = "curl" } } # Now write this to a file (as an example of a resource) resource "local_file" "cache" { filename = "cache.${var.stage}.txt" content = data.http.weather.response_body }

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

For me personally tmux giver minor improvements (some of them are done by some terminals, some are not), e.g.:

* Text selection using variuos shortcuts (usually I use it only for URL):

https://github.com/tmux-plugins/tmux-copycat

* FZF autocompletion from output, e.g. in case I want to diff some file I see changed in `git status`:

https://github.com/laktak/extrakto

The final workflow that comes to mind is using https://github.com/tmux-plugins/tmux-copycat and the prefix + ctrl-f command to jump between file paths, which could provide a faster way to get your file path from command output in tmux into vim.

tmux-plugins/tmux-copycat - A plugin that enhances tmux search. You should install gawk if you haven't already. As of tmux 3.1, regex searches are now natively supported. However, search result highlighting and predefined searches are reasons enough to keep using tmux-copycat.