garmin is arguably one major smart watch vendor and has a great battery life

Garmin is more fitness tracker than smartwatch.

I take it you don’t have a garmin? You can play music directly from it (spotify, YouTube music, etc apps). You get phone notifications, can respond to text messages, make payments, and newer versions include LTE. They are absolutely a smart watch.

Does it last 2 weeks with that kind of usage?

My Enduro 2 lasts around that long, with about 1.5-2 hours of daily GPS tracking for running, part of 4 hours total exercise tracking per day, and underlying background fitness data collection (HR, respiration, temperature etc. including sleep).

As I write, it's at 37% with 6 days left of charge. And it charges 0 to 100% in around 2 hours.

I used to use a fancy Movado / Android Wear watch that without word of a lie could die before 8pm on almost minimal use. It was an absolutely redundant item to own.

Yup. Garmin battery life is insane. I keep seeing people comment how they charge their watches on a near daily basis and that's just insane to me.

I charge my fenix 7 solar maybe once a month. My use case is about 10 hours a week of activity tracking, usually trail runs. This goes up to about 20 hours a week in the summer but i dont recharge much more often. I use garmin pay and occasionally listen to podcasts on my watch while running. I also use the on-watch maps quite a bit on my trail runs.

As someone who has only ever had a Garmin, what am I missing from other smartwatches?

Charging it up every night.

based on these comments, bad battery life?

I get notifications for text messages, phone calls, and emails on my VivoActive 6. There are also good apps; for instance, the built-in (free) golf app is great. Battery lasts over a week, too. So far, I'm pretty happy with it and don't feel the need to get an Apple Watch which requires charging every day.

I'd say Garmin has all of the features a smartwatch typically has that are worth having (notifications, fitness tracking, basic controls ie. music).

For anything else, smartwatches are simply too awkward and small for any real use. Better just to spend a second or two to get your phone out.

when possible (python, golang and many others) I just go and read the source..

I wonder why people come to conclusion like that to that specific problem.

surely the user may knows that there is probably zillions (by that i mean a lot) of users using gmail via IMAP (at least the enterprise accounts) don't you think it's maybe something else you are doing that flags your account

The main point is that a paying customer shouldn't have to guess at why they were flagged.

This Omarchy remind me of Linux-Mandrake from back in the day, a collection of badly written shell script but that "works"

i wish python had something liek that to be honest

one can dream but i wouldn't keep high hopes. I feel functional patterns are left as second class citizens in python.

you have a .deb there https://www.microsoft.com/en-us/edge/download?form=MM145U (i don't use it, just saying)

If it were a longstanding bug versus one just created for this exercise a git diff may not help much. Imagine you've found some edge case in your code that just hadn't been properly exercised before. It could have been there for years, now how do you isolate the erroring section? This technique (or the one I mentioned in my other comment which is very similar but uses more data) can help isolate the problem section.

git diffs can definitely help with newer bugs or if you can show that it's a regression (didn't error before commit 1234abcd but did after).

"Wait, what did I change that impacted that test?"

An intersection between code coverage and a git diff once answered that handily for me.

nice idea but i get that error when i try to use the docker image (on a nixos env)

NameError: name 'SRE_FLAG_TEMPLATE' is not defined. Did you mean: 'SRE_FLAG_VERBOSE'?

(using the mentioned docker command on README $ docker run --rm -v `pwd`/nginx.conf:/etc/nginx/conf/nginx.conf getpagespeed/gixy /etc/nginx/conf/nginx.conf)

:! itself has not been stripped from neovim, it's the "interactive" :! that has been stripped (as the OP said)

i.e if you do :!bash in vim you enter bash in neovim you won't

Thanks for the clarification. That makes sense and seems like a reasonable change to me.

I wouldn't say that `:!bash` is the most illustrative example of its impact. It bites you when you run any command that spits out a prompt, most commonly a [Yn] prompt. You can't use `:!` for these in nvim.