/b/ - Boring

>MK7 cheats coming next week
>Gold mii qr code coming a week after that
>Published on Sep 18, 2015
never ever

>>28

I know, I got lazy. I'll throw it at ya'll eventually.

>Not using Windows NT 4.0
What the fucking fuck man

open source or it's a fucking confirmed botnet

>>38
Assuming you use a sane operating system, and this imageboard has code tags:
[code]#!/bin/bash
for f in *"$1"*; do
mv "$f" "$(dd if=/dev/urandom count=1 bs=16 | base64 | cut -c-15 2> /dev/null).${f##*.}"
done[/code]
Save it as a script. Run it while you're in the directory you want to randomize. If there's a first argument, it only renames files with that argument in their name somewhere.

If files don't have an extension it fucks up. I can fix that if you want.

This took around a minute to write. But I hope you're proud of your version, Huntereb. :^)

>>39

That's not the use of this tool, that script would generate a garbage file name for every file. The one I posted keeps the original file names, and just swaps them amongst the files.

It doesn't have code tags apparently, let me see if I can fix that.

>>43
Ah, my mistake. That makes it harder to do with a shell script. Probably not impossible, but spaces become a real issue.

>>44

I'm sure it could be done, but C# makes everything easy, and GUI's are nice. lol

>>45
It's mostly that shell scripts are a pain compared to all other languages that are still in use. Even plain C might be easier for this. Shell is a language that's based on something that was designed for interactive use 45 years ago, and it can't be overhauled for compatibility reasons.

If $f is a variable, you would expect that

rm $f

would run rm with the contents of $f as its first argument. However, if $f happens to contain spaces, it runs all the different parts of $f as different arguments to the command. If you want to avoid that, you can use this:

rm "$f"

Shell also has the $() syntax, which runs a command and substitutes for the output of that command. If that command outputs a list of filenames, there's no way to tell whether a space is part of the filename or one of the separators.

rm "$(cat file)"

I end up using it a lot because a shell is a universal interface. On Linux, BSD, etcetera, it's powerful enough to perform any task that doesn't need to involve something graphical, plus a lot of tasks that do involve something graphical. You can turn any sequence of shell commands into a script, which is extremely useful for controlling your system.

But it sucks for complicated, reliable scripts.

>>46

Yep, nicely put. Unix commandline is a lot more in-depth than Batch, which is what I usually work with, because everything I need for the things I commonly do is available on Windows. Though, since Linux doesn't "just werk", I've had to resort to what I'd call "hacky shit" using shell scripts at startup and such. Though, it's not really as gross as I feel it is, it just feels unclean for some reason.

And yeah, once you get to more complicated stuff, it'd probably be easier to make things in compiled languages. Or maybe Python or some trash…

>>39
I think python would be the way to go here

>>27
You didn't witre a fuckin function
KeKs