If the file is names bashf I can run it with `bash bashf`.
If I try to run `bashf` then I get an error:
"bash: syntax error near unexpected token `newline'"
If I put the ".sh" extension back on, I can run it simply with `bashf.sh`.
Do you have another file called bashf lying around?
How do you write a shell script that change the extension of all the files?
e.g
chext rtf doc
where .rtf is the original extension
and .doc is the new extension
is it something to do with basename?
do I need a for loop?
Please help!
Unix SuperNewbie (4 Replies)
Hi
I am writing a script which does an FTP of a set of files onto another machine and then would have to rename the files into a different extension on the source machine.
for example if the file being sent via FTP is sample.txt. Once the file has been transferred i would want to modify the... (2 Replies)
Can anyone tell me the easiest way to append an extension (ie. .ldr) to all files in a directory that do NOT have an extension? The directory contains files with and without extensions, however I'm only interested in the files with NO extension.
Thanks. (3 Replies)
Hi,
I need a help regarding a small requirement. I have a list of C files. I need to put them in a file but without .c extension.
say if I have the files as file01.c, file02.c, file03.c etc
My file say cfiles should have
file01
file02
file03
...
...
etc
Appreciate your quick help on... (3 Replies)
I am currently scanning a directory with a shell script to look for all files with a .sh extension. I am wondering how to make it look for more then one extension. For example all .sh, .conf, and .sql files?
Currently this is what I am doing....
find... (3 Replies)
trying to copy all the files without extension then add
"*.txt" but its not working is there any other way and i do not want to use
cpio -vdump just want to use copy command
FROM=/usr/share/doc
TO=/aleza/doc
#the follow function copies all the files without extensions
call(){
cd $FROM... (3 Replies)
i have a file abc.dat that has the below content
abc.dat: -
123.dat
now,
i want to print/output only the below
123
from the file content.( see..i want to chop off .dat extension)
kindly advise on this in ksh-
i just want to the flag i should pass to the cat command - (2 Replies)
Ok I have a PERL script that reads an .xml file. One of the new services listed in the file, is alot longer than the others. I am trying to get a way for the spaces of the Service module to read the .xml file and set the length of the %s to the longest Service
my $jmsfn = "jms-connection.xml";
... (2 Replies)
Hi All,
I want to fetch the files based on .done file and display the .csv files and Wil take .csv files for processing.
1.I need to display the .done files from the directory.
2.next i need to search for the .Csv files based on .done file.then move .csv files for the one directory
... (2 Replies)
Discussion started by: girija.g6
2 Replies
LEARN ABOUT DEBIAN
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS --help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities CHECKBASHISMS(1)