Help with reading directory paths with spaces from a file
Hi I want to know how to handle the spaces in the below scenario.
I have a file (CON_zip_path_1.txt) which has some directory paths with spaces in directory names . My requirement is to unzip these zip files to
another path. Please see the code below and the error.
CON_zip_path_1.txt file contents -there are 9 directory path records with spaces in folder names:
Code:
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218812.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218800.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218600.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218563.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218553.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218556.zip
/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218559.zip
/Contract Workspaces/2017/May/CW221xxxx/CW22184xx/CW2218471.zip
/Contract Workspaces/2017/May/CRW221xxxx/CRW22184xx/CRW2218451.zip
Code:
src_path=/informatica/apps/logs/fin/ote/SrcFiles/Source/Contracts20170706092332/Contracts20170706092332 ;
while read line; do
echo $src_path$line
unzip $src_path$line -d $src_path/Contract\ Workspaces
done < $src_path/CON_zip_path_1.txt ;
error output :
Code:
/informatica/apps/logs/fin/ote/SrcFiles/Source/Contracts20170706092332/Contracts20170706092332/Contract Workspaces/Contract Repository/TCW1000 to TCW9999/TCW1000 to TCW1999/TCW1000 to TCW1099/TCW1000 to TCW1009/CW2218812.zip
unzip: cannot find or open /informatica/apps/logs/fin/ote/SrcFiles/Source/Contracts20170706092332/Contracts20170706092332/Contract, /informatica/apps/logs/fin/ote/SrcFiles/Source/Contracts20170706092332/Contracts20170706092332/Contract.zip or /informatica/apps/logs/fin/ote/SrcFiles/Source/Contracts20170706092332/Contracts20170706092332/Contract.ZI
Dear All,
I'm trying to write a script that searches thru a directory looking for a most recent file and then scp that file.
I have the scp working, but I don't know how to browse the directory and select the most recent file.
The file name includes a date & time stamp (e.g.... (3 Replies)
i have a file in unix having data like
cat
dog
(having spaces in the beginning)
when i read it in a shell script
cat file_name |while read line
do
echo $line
done
it will print
cat
dog
spaces at the beginning are removed....
i dont want these spaces to be... (2 Replies)
Hi
I am trouble parsing through a file with spaces in the filename. I need to grab "supportIDPS/SCM/windows_install/file groups/dds.fgl" and then do a md5sum on it. I am using sh.
Any help is appreciated.
Here is an example of the input file:
7eedbc9f7902bf4c1878d9e571addf9a ... (4 Replies)
Hello,
I found the mimesender multiple attachment emailing shell script in the FAQ of these forums, and I have been able to use it to send multiple files, but only if they don't have spaces in their file name or path.
When I attempt to send a file with spaces in it's name, enclosed... (0 Replies)
I have a script that generates a variable with the location of a file and its complete path. What i want to do is to "cd" to the directory where that file is located using the path name of the file. GIS has absolutely failed me.
For example when i run my script it generates a variable called... (1 Reply)
Hi!
I would like to funnel a series of directories and subdirectories into a text file. This is the output I would like to see from a find command:
/mypath/ABC_01/VISIT_01
/mypath/ABC_01/VISIT_02
/mypath/ABC_01/VISIT_03
/mypath/ABC_02/VISIT_01
/mypath/ABC_03/VISIT_01
I've tried:
find... (2 Replies)
consider the small piece of code
while read line
do
echo $line
done < example
content of example file
sadasdasdasdsa erwerewrwr ergdgdfgf rgerg erwererwr
the output is like
sadasdasdasdsa erwerewrwr ergdgdfgf rgerg erwererwr
the... (4 Replies)
Hello all,
I am new to scripting and here is what I want to get done.
I need to run some processing on many files. I have a whole bunch of files among which there are a few that I am interested in. What I need to do is to write a script which reads the file paths from a text file. line by... (1 Reply)
Hi all my very first post so go easy on me!!
I am trying to build a very simple script to list a file path with spaces in. But I can't get around this problem. My script is as follows:
#!/bin/bash
X="/Library/Users/Application\ Support/"
LS="ls"
AL="-al"
$LS $AL $X
The response I... (5 Replies)
GIT-RM(1) Git Manual GIT-RM(1)NAME
git-rm - Remove files from the working tree and from the index
SYNOPSIS
git rm [-f | --force] [-n] [-r] [--cached] [--ignore-unmatch] [--quiet] [--] <file>...
DESCRIPTION
Remove files from the index, or from the working tree and the index. git rm will not remove a file from just your working directory. (There
is no option to remove a file only from the working tree and yet keep it in the index; use /bin/rm if you want to do that.) The files being
removed have to be identical to the tip of the branch, and no updates to their contents can be staged in the index, though that default
behavior can be overridden with the -f option. When --cached is given, the staged content has to match either the tip of the branch or the
file on disk, allowing the file to be removed from just the index.
OPTIONS
<file>...
Files to remove. Fileglobs (e.g. *.c) can be given to remove all matching files. If you want git to expand file glob characters, you
may need to shell-escape them. A leading directory name (e.g. dir to remove dir/file1 and dir/file2) can be given to remove all files
in the directory, and recursively all sub-directories, but this requires the -r option to be explicitly given.
-f, --force
Override the up-to-date check.
-n, --dry-run
Don't actually remove any file(s). Instead, just show if they exist in the index and would otherwise be removed by the command.
-r
Allow recursive removal when a leading directory name is given.
--
This option can be used to separate command-line options from the list of files, (useful when filenames might be mistaken for
command-line options).
--cached
Use this option to unstage and remove paths only from the index. Working tree files, whether modified or not, will be left alone.
--ignore-unmatch
Exit with a zero status even if no files matched.
-q, --quiet
git rm normally outputs one line (in the form of an rm command) for each file removed. This option suppresses that output.
DISCUSSION
The <file> list given to the command can be exact pathnames, file glob patterns, or leading directory names. The command removes only the
paths that are known to git. Giving the name of a file that you have not told git about does not remove that file.
File globbing matches across directory boundaries. Thus, given two directories d and d2, there is a difference between using git rm 'd*'
and git rm 'd/*', as the former will also remove all of directory d2.
REMOVING FILES THAT HAVE DISAPPEARED FROM THE FILESYSTEM
There is no option for git rm to remove from the index only the paths that have disappeared from the filesystem. However, depending on the
use case, there are several ways that can be done.
Using "git commit -a"
If you intend that your next commit should record all modifications of tracked files in the working tree and record all removals of files
that have been removed from the working tree with rm (as opposed to git rm), use git commit -a, as it will automatically notice and record
all removals. You can also have a similar effect without committing by using git add -u.
Using "git add -A"
When accepting a new code drop for a vendor branch, you probably want to record both the removal of paths and additions of new paths as
well as modifications of existing paths.
Typically you would first remove all tracked files from the working tree using this command:
git ls-files -z | xargs -0 rm -f
and then untar the new code in the working tree. Alternately you could rsync the changes into the working tree.
After that, the easiest way to record all removals, additions, and modifications in the working tree is:
git add -A
See git-add(1).
Other ways
If all you really want to do is to remove from the index the files that are no longer present in the working tree (perhaps because your
working tree is dirty so that you cannot use git commit -a), use the following command:
git diff --name-only --diff-filter=D -z | xargs -0 git rm --cached
EXAMPLES
git rm Documentation/*.txt
Removes all *.txt files from the index that are under the Documentation directory and any of its subdirectories.
Note that the asterisk * is quoted from the shell in this example; this lets git, and not the shell, expand the pathnames of files and
subdirectories under the Documentation/ directory.
git rm -f git-*.sh
Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not remove
subdir/git-foo.sh.
SEE ALSO git-add(1)GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-RM(1)