I wouldn't test for filenames containing spaces, tabs, or newlines, I'd just write code that works even if they are present. (And if I found users creating filenames containing whitespace characters, I'd ban them from using my system! Unfortunately, there need to be exceptions for some things like .mp3 and .mp4 files with spaces in the titles of songs and movies, but most users creating filenames containing spaces are just trying to create problems for inexperienced programmers.)

Stop trying to create lists and then trying to process the list. Process filenames one at a time. And, learn to use shell built-ins instead of pipelines of awk, grep, and ls commands. Try something more like:

Code:

#!/bin/bash
# Assume that we are starting in a directory with a filename suffix ".git".
# Get related non-".git" directory name.
FOLDER_NAME=${PWD##*/}		# Extract last component of current working directory
FOLDER_NAME=${FOLDER_NAME%.git}	# Throw away ".git".

printf 'DEBUG: VAR FOLDER_NAME=%s\n' "$FOLDER_NAME"

# Process the files in the non-".git" directory...
for FILE in ../"$FOLDER_NAME"/*
do	# Skip files that are not regular files...
	[ ! -f "$FILE" ] && continue

	# Do whatever you want with the regular file from ../"$FOLDER_NAME"...
	printf 'DEBUG: VAR FILE="%s"\n' "$FILE"
	printf 'another file inside the FOR loop\n:'	# Should ":" be before newline?
done

If you don't understand how something in the above works, try running it with:

Code:

bash -xv script_name

and watch how bash processes each command in the script. If you still don't understand, ask questions... We're here to help you learn.