wttr.in VS tmux-resurrect

#!/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/ ?

I use https://github.com/tmux-plugins/tmux-continuum and https://github.com/tmux-plugins/tmux-resurrect to restore all my tmux sessions if I reboot my machine or kill tmux.

tmux-resurrect and tmux-continuum are the utils I use to persist sessions across reboots. They have keybinds and options to make it either automatic or manual, but they save EVERYTHING down to the Neovim session (if you use those) for the session's working directory

This would be my first go-to: https://github.com/tmux-plugins/tmux-resurrect

I hardly reboot a machine unless I am intending to, but there are plugins for tmux for this too.

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

And to save and restore tmux sessions automatically, I use tmux-resurrect + tmux-continuum.

You must use all 3 of: tmux-continuum tmux-resurrect vim-obsession

Sure. Once you log in to the remote Linux machine, just run `tmux` and do your job. When you connect to the remote Linux machine next time, run `tmux attach`, and you will be right where you left off. The sessions will be persisted until you restart the Linux machine (well, or kill the tmux server). If you'd like even more persistence after machine restart, you can also try https://github.com/tmux-plugins/tmux-resurrect