lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@lyse does not follow you (they may not see your replies!)

Recent Twts

Recent twts from lyse

lyse @lyse.isobeef.org
 (2d ago)

(#lpzuytq) @kat@yarn.girlonthemoon.xyz Ta! The dead end wasn’t all that bad in my opinion. Personally, I really do like dirt paths and exploring. It was all dried up, so no muddy mess we had to walk through. More like climbing over thick branches that have been worked into the ground by harvesters or forwarders in the muddy winter. Rough terrain. My mate, on the other hand – whose idea it was to check out the real summit in the first place ;-) — wasn’t all that pleased about the detour. Oh well. :-D

#h4xhphq
lyse @lyse.isobeef.org
 (4d ago)

(#z27c4ya) @kat@yarn.girlonthemoon.xyz I only listened to you while going through my photos, so I did not pay very close attention. :-)

Since you have a proper server – haha, not just one – and hence are not limited, I suggest you learn a real programming language and don’t waste your time with this PHP mess. It might have improved a wee bit since I was a kid, but it felt like some hacked together shit. The defaults also were questionable at best, it was easier to hold it wrong than right. This stands testament to bad design and is especially terrible from a security point of view.

You’re right, programming is like any other craft. You only truly learn by actually doing it. And this just takes time. Very long time to master it. Or as close to as it gets. The more you know, the more you realize what else you don’t know (yet). It’s a never ending process. So, take it easy, don’t get discouraged, happy hacking and enjoy the endeavor! :-)

#v36n74q
lyse @lyse.isobeef.org
 (4d ago)

We had sun, clouds, wind, rain and a whole lot of fun on our trip to the Wasserberg. We’ve been out seven hours in total, not bad at all for all those kilometers. We added on some detours to check out a pond I’ve been introduced by a mate a few years back.

After some (expensive) tucker at the Wasserberghaus, we tried to actually visit the summit this time. However, there’s nothing to see, just a rough logging trail (46-49). That was a dead end, so we had to turn around. It was some nice exploring, but I reckon this was my first and last time up there. :-)

Unfortunately, we didn’t go to the neighboring Fuchseck this time, only the Wasserberg with some extras.

https://lyse.isobeef.org/wanderung-auf-den-wasserberg-2025-05-18/

#aicxxda
lyse @lyse.isobeef.org
 (1w ago)

(#dh3tfwq) @kat@yarn.girlonthemoon.xyz You don’t need to change the directory first in line 11, you can just create the directory, that’s sufficient since you’re having an absolute path.

The echo in line 13 is useless, you can simplify this to: newdir="$WD/$now" If you reversed this line with the previous one, you could make use of the variable in the directory creation: mkdir "$newdir".

In line 16, pull the directory change out of the loop upfront. The loop body doesn’t modify the working directory, so no need to reset it with each cycle. In fact, you could even spare the cd altogether when you simply tell find where to look: find "$basedir" -type f….

I didn’t try it, but if I read the manpage correctly, you should be able to simplify line 19 as well:

-C Change to DIR before performing any operations. This option is order-sensitive, i.e. it affects all options that follow.

Hence, remove the cd and put the -C "$WD" as the first argument to tar. Again, I didn’t try it. Proceed with caution.

Finally, you don’t need to specify the full path to rm in line 21. I bet, /bin is in your PATH. When you removed the previous cd from my last suggestion, the relative path that follows won’t work anymore. So, just use the absolute path that you already have in a variable: rm -rf "$newdir"

I hope you find this tiny review a wee bit useful. :-)

#xbntaca
lyse @lyse.isobeef.org
 (1w ago)

(#sywawja) @kat@yarn.girlonthemoon.xyz @movq@www.uninformativ.de @prologic@twtxt.net Yeah, I’m also having them in my repertoire for ages, so I’m used to the weird command line options. From today’s perspective, they’re not consistent with the rest of the typical shell utilities, that’s for sure.

Regarding find | grep foo, I recommend find -name '*foo*', prologic. Also, I regularly use -type d and -type f to find directories or files.

#2livc3a