harsh3466 @ harsh3466 @lemmy.world

Posts

5

Comments

162

Joined

2 yr. ago

I didn’t k ow there were dms leak issues. I will investigate. If I’m finding that I’ll likely switch back to openvpn

I’ve heard of oh-my-zsh, but I haven’t wanted to deviate off of bash until I have a good grasp on bash first.

I will look into that. Thank you!

I’m glad they’re useful for you!

Ohhh. Thank you. I will give that a read through!

That’s what I’m finding. I’m not certain I need regex for what I want to accomplish with find. I’m reorganizing my media libraries, and I have a mix of mp4 and mkv files. I want to be able to find all mkv and mp4 files and move them using regex like '.+\.(mp4|mkv)'

I have learned how to use find with -exec and -delete, but I haven’t gotten to -print0 or xargs yet.

I’ve never used git to publish/make myself a repo before. That’s something I’ve been meaning to learn but haven’t quite gotten there yet. However, with the amount of tinkering, and breaking I’ve been doing, I think I’ll move it up on my priority list.

I’ve also got shell scripts I’ve been writing and tinkering with and having proper version control (versus script, script.copy, script.copy.bak…) would also be nice.

That’s a super useful way to remember. Thank you!

I didn’t know that tool existed I will give fzf a try!

I agree, and I’d like to be there as well so that I can easily read and understand a man page.

1. Agree. Always was too strong a statement. I’ll edit my post to reflect that.
2. Thank you! I’m going to read up on string manipulation
3. True. This has been working for me because I know enough of the directories I’m looking for to insure a single match, but not the necessarily the exact, specific directory name.

That’s fair. Always was probably too strong.

To insure the script works on the files you want it to work on.

If you use a relative path in a script (is relative the right word?), with something like:

mv *.txt /place/to/move/to/

The script will act on the files in the current working directory, which may not be the files you intend for the script to act on.

If you put the absolute path to where the files reside in the filesystem, then you can run the script from any location, and know that it will act on the files in the specified directory.

Maybe always is too strong a statement. For the scripts I was working on, it was a learning moment when I ran the script without the full path and the script errored out because the files were not in the working (home) directory. (I had ssh’d into the machine to run the script)

You’re welcome! I stumbled across Multipass when I was looking for virtual machine options for the m1 mac mini I’m working on. I specifically was trying to get away from using the mac coreutils for a consistent syntax experience, and Multipass has been working perfectly for that.

It was only after I’d been using Multipass already that I stumbled across that script, and planned to take a look at it to possibly implement on my machine. I didn’t realize that Homebrew allowed for replacing the coreutils with the GNU versions. Another thing learned!

Yes, thank you! The man pages have been a huge help as I’m working through things. Sometimes I don’t know enough to understand what the man pages are telling me, and then I usually end up on stack exchange looking at a command example that someone has helpfully broken down.

Nice. I haven’t seen that one before!

Obligatory xkcd

My initial goal (before learning what a headache rar is) was to preserve the original file format. Now my plan is to convert them. I have to confer with my friend to see what format they’d prefer for the files. Probably end up using regular old zip.

This sounds interesting. I’m gonna look into it. Thank you!

Haha. Definitely last resort. Having learned what a pain rar is due to its propriety nature, I’m going to see if they care if I convert them to tar or zip first.