lgogdownloader VS Mosh

I use https://github.com/Sude-/lgogdownloader it is for Linux however. You can probably run it in WSL though.

If you have access to Linux, there's a community tool called LGOGDownloader that can download your whole library or selected parts of it in one go. It can also list any local files that aren't in your GOG account anymore, e.g. older versions of updated games. I use it regularly to keep my offline library of 600+ games up to date.

My local GOG library is maintained by the third-party LGOGDownloader. I'm using GOG Galaxy only for a handful of Windows games that do require it for multiplayer.

I recently discovered that my GOG downloader (https://github.com/Sude-/lgogdownloader) is currently broken, I've updated to the latest version but it seems GOG changed their API?

No idea if it runs on windows, but for linux there is https://github.com/Sude-/lgogdownloader/ i download all my games with this command:

Nice! How does this compare to lgogdownloader? (https://github.com/Sude-/lgogdownloader)

https://sites.google.com/site/gogdownloader/ I found it in my AUR repository so I expect it to be in the repository of whatever distribution you might choose.

There actually is lgogdownloader, which apparently implements part of the GOG Galaxy API, but it seems to only do listing, downloading, and installing of games, and not whatever else Galaxy does.

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.