Skip to content
This repository has been archived by the owner on Mar 19, 2023. It is now read-only.

Latest commit

 

History

History
320 lines (223 loc) · 10.4 KB

readme.md

File metadata and controls

320 lines (223 loc) · 10.4 KB

Creating Folder and Move Files under Same Name Automatically

Warning

Basic knowledge in command scripting (cmd, sh, or ps1) is required

Tip

You can also download directly the script with the link provided after code block.

Comparison scripting languages by supported operating system

Some operating systems only support one type of the command scripting language, or it can be supported by installing separately from first party or third.

This comparison cheatsheet is intended to make thing clear as we have tested in several operating systems.

tl;dr table

Language Windows ReactOS DOS macOS Linux BSD/*nix BeOS/Haiku
Batch (.bat) ✔ ✔ ✔ 👥 👥 👥 👥
PowerShell (.ps1) ✔ 🤔 🤔 📥 📥 👥/📥 👥
Shell (.sh) 👥 👥 ❌ ✔ ✔ ✔ ✔

Tip

Read detailed info to know more about them.

Emoji Legends

Emoji Descriptions
✔ Available Natively
📥 Need to be installed manually first from the 1st party
👥 Need to be installed manually (a client) first from a 3rd party
🤔 Unknown, but there's a possibility with a workaround
❌ Not supported

Detailed info

Batch .bat file

Windows

Status: ✔ Supported
Source: Native

Description:
Supported since day one of Windows... No joke.

ReactOS

Status: ✔ Supported
Source: Native

Description:
tl;dr, its Windows, but open source. It should be work fine.

DOS

Status: ✔ Supported
Source: Native

macOS

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Virtual machine

Description:
Use any virtual machines app (or WINE for MacOS, Parallel Desktop, or Codeweavers CrossOver) to run Windows Command Prompt.

Linux

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Virtual machine

Description:
Use any virtual machines app (or WINE or Codeweavers CrossOver) to run Windows Command Prompt.

BSD/*nix

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Virtual machine

Description:
Use any virtual machines app (or WINE or Codeweavers CrossOver) to run Windows Command Prompt.

BeOS/Haiku

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Virtual machine

Description:
Haiku OS (port of BeOS) known in the beta stage (I think). iirc, there’s no app for users to have virtual machines. But, because I see Haiku is able to run Bash Shell script, maybe there’s an app that requires to build from source code), CMIIW. ¯\_(ツ)_/¯

Note

After further investigation on October 21, 2020, it seems qemu (an open source emulator) app was ported to Haiku OS (but not BeOS since it was discontinued). So installing Windows OS via qemu and using command prompt is possible.

PowerShell .ps1 file

Windows

Status: ✔ Supported
Source: Native

Description:
Started from Windows Vista, PowerShell terminal was installed by default.

ReactOS

Status: 🤔 Unknown
Possible status: 📥Need to be installed manually first from the 1st party. / 👥 Need to be installed manually (a client) first from a 3rd party
Source: Install 1st party app, Virtual machine

Description:
Because ReactOS is backward-compatible with Windows apps, installing PowerShell onto ReactOS should be able to run properly. This hypothesis has not been tested yet. Maybe you need to try to install the PowerShell Windows version on React?

DOS

Status: 🤔 Unknown
Possible status: ❌ Not supported

Description:
Well, because DOS is actually very old and I bet no one uses DOS (except if you’re a masochist tech geek, so you’re using DOS? :P), this method has not been tested yet. As far as I know, there’s no port of PS to install/embed it into the system.

macOS

Status: 📥 Need to be installed manually first from the 1st party
Source: PowerShell/PowerShell

Description:
Download LTS release.

Linux

Status: 📥 Need to be installed manually first from the 1st party
Source: PowerShell/PowerShell

Description:
Download LTS release.

BSD/*nix

Status: 📥Need to be installed manually first from the 1st party. / 👥 Need to be installed manually (a client) first from a 3rd party
Source: PowerShell/PowerShell

Description:
Download the official source code here. However, Microsoft/PowerShell team does not provide an official guide on how to build PowerShell for BSD, UNIX, nor UNIX-like OS. The best way is to use any VM or WINE on your machine.

Edit: but why do you want to make yourself get trouble if you do have a Bash supported terminal on your system LOL?

BeOS/Haiku

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Virtual machine

Description:
See § BAT support on Haiku/BeOS.

Shell .sh file

Windows

Status: 📥Need to be installed manually first from the 1st party. / 👥 Need to be installed manually (a client) first from a 3rd party
Source: Windows Subsystem for Linux (WSL), Git Bash, Cygwin, Virtual Machine

Description:
To install Bash Shell compatibility to Windows OS, you need to install Git for Windows (complete), any Linux distro on Microsoft Store with WSL 2 turned on (only for Windows 10 version 2004, build 19041.450), or Cygwin. I recommend installing Git for Windows (for anyone), or WSL if you understand the Windows-Linux ecosystem.

ReactOS

Status: 👥 Need to be installed manually (a client) first from a 3rd party
Source: Git Bash, Cygwin, Virtual Machine

Description:
See § SH support on Windows.

DOS

Status: ❌ Not supported

macOS

Status: ✔ Supported
Source: Native

Linux

Status: ✔ Supported
Source: Native

BSD/*nix

Status: ✔ Supported
Source: Native

BeOS/Haiku

Status: ✔ Supported
Source: Native

Using Batch file format

  1. Create a new bat (.bat) file with notepad by copying those line of codes.

     @echo off
 setlocal EnableDelayedExpansion
 rem Change to working directory.
 pushd "E:\5"
 rem Don't forget to modify filetype below this comment
 rem I mean,   vvv that one.
 FOR %%G IN (*.png) DO (
     rem edit  ^^^ this first lol
     FOR /F "tokens=1 delims= " %%a IN ("%%G") do (
         set "outFolder=%%a"
         for /D %%i in (*.*) do (
             for /F "tokens=1 delims= " %%b IN ("%%i") do (
                 if "%%a"=="%%b" set "outFolder=%%i"
             )
         )
         if not exist "!outfolder!" md "!outfolder!"
         move "%%G" "!outfolder!"
     )
 )
 popd
 pause

    Save those lines of code as .bat file to working directory. If applicable, use UTF-8 encoding with CRLF line ending for the script itself.

  2. On pushd "E:\5", change to the working directory.

  3. On FOR &&G IN (*.png) DO ( code line, change .png to current file format. Otherwise, you may continue.

  4. Run the script.

Using PowerShell file format

  1. Create a new PowerShell file (.ps1) file with notepad, gedit, or any text editor (preferably code editor), and copy-paste this script:

     # Change to working directory
 $dir = "E:\5"

 $filelist = @(Get-ChildItem $dir)

 ForEach ($file in $filelist){
     # Get the Username part
     $folder = $file.Name.Split("-")[0]

     #Test if the folder exists.
     Set-Location ($dir+'\'+$folder)

     #If there is no folder, create a folder.
     if(!$?){ mkdir ($dir+'\'+$folder) }

     #Move items, keeping the same name.
     Move-Item $file.FullName ($dir+'\'+$folder+'\'+$file.Name)
 }

    Save those lines of code as a .ps1 file to the working directory. If applicable, use UTF-8 encoding with LF line ending for the script itself.

  2. On $dir = "E:\5", change E:\5 to a working directory. Save the file after modifying the directory path.

  3. Run the script.

Using Shell file format

  1. Create a new shell (.sh) file with notepad, gedit, or any text editor (preferably code editor), and copy-paste this script:

     #Change `.png` to your working extension file, like `.psd`
 for f in *.png; do
     name=`echo "$f"|sed 's/ -.*//'`
     dir="$name"
     mkdir -p "$dir"
     mv "$f" "$dir"
 done

    Save those lines of code as .sh file to the working directory. If applicable, use UTF-8 encoding with LF line ending for the script itself.

  2. On for f in *.png;, change current file format (on PNG). Otherwise, you may continue.

  3. Open terminal.

  4. Specify working directory with cd.

  5. Follow these steps:

    • If your .sh file is inside of your working directory, type ./<NAME OF YOUR SCRIPT FILE>.sh with <NAME OF YOUR SCRIPT FILE> is your script file, ofc. Then press enter to proceed.
    • But, if your script is outside of the working directory, change ./ to ../, a.k.a add one more dot.

Notice that your file name format is following this: <Username> - <CardId> [Specification].<FileFormat> Dash between username and other text is required. Otherwise, you’ll get bonked by system.