Bash Fullpath

All,

From the directory:

/home/$user/.thunderbird/$profile/ImapMail/

I'm running the cmd:

ls -aR /home/$user/.thunderbird/$profile/ImapMail/ | grep -i $dir

In this case $dir=sent and so I get:

Sent.msf
Sent Mail
Sent Mail.msf
Sent-1
Sent-1.msf
Sent.msf
Sent Mail
Sent Mail.msf
Sent.msf
Sentry Telecom
Sentry Telecom.msf
Sentry Telecom
Sentry Telecom.msf
Sent
Sent.msf

I need to process the files that have no extensions, yes they are files, not directories. However the directory:

/home/$user/.thunderbird/$profile/ImapMail/

contains the following subdirectories:

imap.gmail.com
imap.gmail-1.com

In order to process the files I have to have the full path & filename, but all the HOWTOs I've looked at talk about "fullpath" in all other terms from what I need.

If you either know how to do this, or know the right HOWTO, please pass along the info, so I can finish my script.

Thanks!

TBNK

All,

The files that will process from this list are:

Sent Mail
Sent-1
Sent Mail
Sentry Telecom
Sentry Telecom
Sent

But these are not dups, but in different subdirectories.

The code that will process on these will be:

grep '^\(From\|To\|Cc\|CC\Bcc\|BCC\):' $fullfilename grep -o -E '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,4}' | sort -f | uniq -i >> $adr_mst;

But cannot process without the fullfilename that includes the fullpath, therefore the output file is always empty.

I have all this working in a hardcoded version, but other users will have directories unique to themselves, so attempting an autofinding version, that all TBird users can use.

Cheers!

TBNK

All,

Able to eliminate the files with extensions with the following code:

		imfil=$(basename "$imdir");
		imext="${imfil##*.}";
		if [[ "$imfil" == "$imext" ]]; then

Because the file basename and the extension are the same value, when there is not file extension.

Cheers!

TBNK

All,

The actual code I'm running is a function:

get_IMdirs () {
	#############################################################################
	# Modified: 	Nyle Davis			Mod Date: 17-04-25
	# Purpose:		Get all "ImapMail" subdirectories
	# Vars:			
	#############################################################################
	declare -a im_ray=();
	declare -a im_dirs=();
	imsub=${dir%:};
	xx=0;
	SAVEIFS=$IFS;
	IFS=$(echo -en "\n\b");
	im_dirs=$(ls -R $imsub);
	for dir in ${im_dirs[@]}; do
		imdir=${dir%:};
		imfil=$(basename "$imdir");
		imext="${imfil##*.}";
		echo "P=> $imsub F=> $imfil E=> $imext";
		if [[ "$imfil" == "$imext" ]]; then
			im_ray[$xx]=${imsub}${imfil};
			echo "IR=> ${imsub}${imdir}";
			((xx=xx+1));
		fi
	done
	IFS=$SAVEIFS;
}	# end function get_IMdirs

where dir='/home/$user/.thunderbird/$profile/ImapMail/'
and has to have the ' for the special chars in the path, which becomes imsub.

Since the files being processed have no extension imfil and imext are an exact match, so processing to add to the array only happens then. However, when the array is to be processed later, that fullfilename, including the fullpath is needed or the file with never be found to process.

It was suggested I use the code:

basedir="/home/$user/.thunderbird/$profile/ImapMail/";
while IFS= read -rd '' path; do
    echo "$path";
done < <(find "$basedir" -iname "${dir}*" -type f -print0)

and while that renders the path it also floods with unwanted information that then has to go through complex filtering to get back to just what is needed.

All suggestions and HOWTOs welcome.

Cheers!

TBNK

if there are spaces (in file/dir names) you ought to use "${var}" everywhere.
For example: imdir="${dir%:}";

the line imsub=${dir%:}; is unclear, dir is not (yet) initialized or ???
imfil=$(basename "$imdir"); can be written as: imfil="${imdir##*/}"
for dir in ${im_dirs[@]}; do should be written as for dir in "${im_dirs[@]}"; do, but while is much better.

while that renders the path it also floods with unwanted information that then has to go through complex filtering to get back to just what is needed.

would be nice to explain what is the problem exactly...

All,

OK modified my code to:

get_IMdirs () {
	#############################################################################
	# Modified: 	Nyle Davis			Mod Date: 17-04-25
	# Purpose:		Get all "ImapMail" subdirectories
	# Vars:			
	#############################################################################
	declare -a im_ray=();
	declare -a im_dirs=();
	imsub=${dir%:};
	xx=0;
	SAVEIFS=$IFS;
	IFS=$(echo -en "\n\b");
	im_dirs=$(ls -R $imsub);
	for dir in ${im_dirs[@]}; do
		imdir=${dir%:};
		while IFS= read -rd '' path; do
			SAVEIFS=$IFS;
			IFS=$(echo -en "\n\b");
			imfil=$(basename "$imdir");
			imext="${imfil##*.}";
			IFS=$SAVEIFS;
			if [[ "$imfil" == "$imext" ]]; then
				basfil=$(basename "$path");
				basext="${basfil##*.}";
				if [[ "$basfil" == "$basext" ]]; then
				  	echo "IF=> $imfil P=> $path";
					im_ray[$xx]=$path;
					((xx=xx+1));
				fi
			fi
		done < <(find "$imsub" -iname "${imdir}*" -type f -print0)
	done
	IFS=$SAVEIFS;
}	# end function get_IMdirs

Appears to be correct, but still testing.

Cheers!

TBNK

All,

Still getting lots of error messages and array appears blank, but not sure I'm doing the assign correctly.

Cheers!

TBNK

you did not tell us anything about those error messages, so cannot help you to fix them.
from the other hand you can insert set -xv at the beginning of the function to see what's happening. Also you may try to use shellcheck to catch problems.
www.shellcheck.net

All,

OK, keep getting errors from the find command of:

find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-iname `/home/$user/.thunderbird/$profile/ImapMail/imap.gmail.com/filename.ext*'' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ `/home/$user/.thunderbird/$profile/ImapMail/imap.gmail.com/filename.ext*''.

So I added the grep -FzZ and nothing improved.

I can't tell if my processing is right with so many errors as this loop over 14,000 times.

Cheers!

TBNK

find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-iname ...' will probably evaluate to false all the time on this system.

interesting!
i never thought about that.