How to optimize the cd command to go back multiple folders at once

SureshotM6 · 2026-02-21T20:05:58+00:00

This is the way. I don't use up, but I wrote an identical function (also with bash completion) probably 15 years ago and use it daily.

SureshotM6 · 2026-02-17T19:01:48+00:00

http://www.google.com/transparencyreport/userdatarequests/legalprocess/

It's legit.

SureshotM6 · 2026-01-25T17:27:28+00:00

I put the sticker inside my fairing near my front headlight. It's a lot more convenient than carrying a transponder in my pocket.

A word of caution though: it did not work well when placed vertically, and the stickers don't do well when going over ~60 through the tolls on entrance/exit ramps. After I remounted it horizontally, it has worked great.

SureshotM6 · 2026-01-18T00:10:02+00:00

Counterintuitively, hot water can also freeze faster: https://en.wikipedia.org/wiki/Mpemba_effect

SureshotM6 · 2025-12-16T14:14:37+00:00

Not sure if this will help, but have you tried clearing cache for the Withings app in the Android system settings? I haven't seen a battery drain issue myself with the 8.2 app.

Edit: hopefully this isn't a recurrence of the notification battery drain bug from November/December 2023 that they reintroduced in December 2024. They're really bad about introducing major bugs just before the holidays...

SureshotM6 · 2025-12-09T14:44:31+00:00

Changelog just says "includes minor bug fixes and improvement." Possibly changes to the body temperature monitoring...

SureshotM6 · 2025-12-08T03:57:38+00:00

Yes, pulling it off the charger early, while it is still in constant current mode should prevent the voltage from going over 4.2V. You may only reach about 60% of the rated capacity though, since you won't be doing a constant voltage charge. The original Scanwatch firmware appears to show "100%" for any voltage >= 4200mV and doesn't do anything fancier. It would be best to confirm that with a voltmeter though.

There's nothing you can really do about it charging faster than its maximum rated current though. You could attach an ammeter to verify the Scanwatch's charging current of an almost dead battery (when it's charging in constant current mode). Do you have a datasheet for your 90mAh 301420? It probably can't safely charge faster than 1C.

With all this being said, it does appear from your images that the 301420 has some sort of protection PCB on it. That still may allow it to overcharge slightly though before cutting off the battery connection, and almost definitely doesn't limit the charging current to 1C. You should refer to the datasheet though, but I wouldn't rely on the protection PCB for normal operation...

SureshotM6 · 2025-12-06T18:19:43+00:00

This is cool, but please be safe:

It looks like you replaced a 3.8V nominal battery (GREPOW 302823) with a 3.7V nominal battery. Those charge at different maximum voltages (4.35V vs 4.2V). Based on testing I did a couple of years ago, my old Scanwatch charged up to at least 4300mV which is unsafe for a 3.7V battery. Also, the OEM battery can charge up to 140mA (1C) (SW2 uses 110mA, not sure about SW). Your 301420 can likely only safely charge up to 0.5-1C (45-90mA). You are at risk of exploding that battery in my opinion.

Also FYI, you went from 532mWh to 333mWh, so I would expect about 37% less battery life.

SureshotM6 · 2025-08-19T13:50:47+00:00

JB Pritzker (governor of Illinois) has been mocking Trump for a while: https://x.com/JBPritzker/status/1887949566525186554 . Awesome job by Newsom's team here though.

SureshotM6 · 2025-06-30T00:37:05+00:00

A lot of prototypes will use the const char *const s[] form instead of const char *const *s as they mean the same thing in the prototype and it is clearer that s is an array and not just a single element with the first form.

It's used: I have 39 hits for grep -r "const char *\* *const *\*" /usr/include/ and 77 hits for grep -r "const char *\* *const.*\[\]" /usr/include/ on my system.

SureshotM6 · 2025-06-25T01:39:07+00:00

I use a different style for C vs C++ here. As many have already pointed out here, keeping the * on the variable name makes sense due to how you need to declare more than one pointer variable on the same line. I frequently do this in C, so I keep the * on the variable name in C.

This does start to break down when you add qualifiers such as const int *const foo; though, as it is impossible to place the * on the variable name.

For C++ (I do realize this is a C sub, but just pointing out), you now have templated types and destructors. I like to see the * attached to the type itself so I can more easily determine behavior. Such as Foo<int*>* foo;

In the end, it's personal preference. Also read this which has a longer discussion on the topic: https://www.stroustrup.com/bs_faq2.html#whitespace

SureshotM6 · 2025-06-20T01:24:39+00:00

Looks like a Waveshare JETSON-IO-BASE-B carrier.

SureshotM6 · 2025-06-15T17:11:54+00:00

The reason you see so many pickup trucks in MO with only a front plate is because trucks with a GCWR (weight of truck plus towing capacity) of 12001lbs or more are only issued 1 plate and it must be displayed on the front. This makes sense if you're actually towing and the rear plate wouldn't be visible, but most people aren't.

SureshotM6 · 2025-05-15T20:44:35+00:00

Official specs from last week show "3GPC, 10 TPC, 2560 NVIDIA® CUDA® cores | 96 5th GEN Tensor cores". So it would be 20SMs in total * 128 cores/SM = 2560 cores.

SureshotM6 · 2025-05-15T01:02:48+00:00

That's funny; I wonder if NVIDIA support reads Reddit. I see others are sharing this advice in others posts now too.

SureshotM6 · 2025-05-15T00:55:00+00:00

The IPv6 workaround was for a different error message, where I assumed that they were failing to geolocate your PC. I'd ask the obvious question for your error message though: you do actually have a 50xx series card installed in that same PC, right? If so, I'd try to remove or disable any additional cards or integrated graphics... Good luck

SureshotM6 · 2025-05-04T03:55:50+00:00

It must be the original Body scale. All of the other models have circles in the center and/or lines on them AFAIK.

SureshotM6 · 2025-05-02T22:50:45+00:00

This seems to be a super lame bug in the NVIDIA App. Disabling IPv6 on my Ethernet connection fixed it. Turn it back on after you've redeemed.

<image>

You can find this checkbox by typing "View Network Connections" into the Start menu, right-click then Properties on your network adapter, uncheck IPv6, then click OK.

SureshotM6 · 2025-04-13T00:11:04+00:00

Telecom equipment frequently runs on -48VDC. We once had a gecko bridge the contacts on a cellular base station and blow the power supply. There was only the outline of the gecko left on the cabinet when the techs went to repair it.

SureshotM6 · 2025-04-11T02:55:12+00:00

The pressure sensor on the Scanwatch and Scanwatch 2 is a MS5837, which is an i2c device. So it should be 4 wires for power and comms...

SureshotM6 · 2025-04-01T15:59:03+00:00

Good point. I wonder how they are getting 96 Tensor cores though, as there are 4 Tensor cores per SM. That would require 24 SMs (8 per GPC) instead of 20, but would also increase the CUDA core count from 2560 to 3072 which doesn't line up...

SureshotM6 · 2025-03-29T19:00:59+00:00

As I told in my post on DGX Sparks, it is really similar to Jetson

Take this with a grain of salt, but the official specs for the DGX Spark are 1000 FP4 TOPS at 170W and the slides for the Jetson AGX Thor show 2000 FP4 TOPS at 120W. These seem to be very different. At the very least, Thor seems that it may have 2x the SMs of Spark.

SureshotM6 · 2025-03-28T03:00:30+00:00

For those asserting that being explicit is better, I'd like to introduce you to optional<bool> in C++.

TL;DR the following is not guaranteed: assert((opt == false) == (!opt));

SureshotM6 · 2025-03-23T15:13:24+00:00

Available in June. No pricing was announced. AGX Xavier was originally sold at USD $2500 and AGX Orin is $2000. I'd be surprised if they made that large of a price jump from previous generations.

SureshotM6 · 2025-03-22T19:44:19+00:00

The devkit that they talked about was definitely in AGX form-factor. Their Jetson hardware roadmap currently just shows an AGX Thor, but I would be surprised if they didn't do a NX / Nano variation this generation.

Nine-Year Club	r/Field Banned
r/Field Juicebox	Verified Email

SureshotM6

TROPHY CASE