11-13-2004
In bourne, ksh, bash, etc, everything between a # and the newline is ignored. This includes a terminal backslash. But you can have as many comment lines as you want. Just start each one with a #.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I m new for linux ... but now i will do this continuously. So my question is how to comment more then 1 line i dont wanna put # to each line.. my script is too big...
or u can tell me that how can i add # to sellected lines means if i wanna put # from line number 10 to 20 then how... (3 Replies)
Discussion started by: ajayyadavmca
3 Replies
2. UNIX for Dummies Questions & Answers
How to comment a set of lines in a script?
we use # to comment a single line , is there ant other cmd to comment a block? (2 Replies)
Discussion started by: rolex.mp
2 Replies
3. Shell Programming and Scripting
HI all
I am working on a script, few details are as follows. I have one properties File and one script. The property file contains the JOBID which are to be executed and the Script runs these jobs ONE by ONE. After completing the JOB I need to comment that job in the property File. This is the... (3 Replies)
Discussion started by: Prashantckc
3 Replies
4. Shell Programming and Scripting
can we use "---------" for commenting......... (2 Replies)
Discussion started by: simmijaswal
2 Replies
5. Shell Programming and Scripting
Hi ,
I have a XML file like this
<dependency>
<groupId>fr.xxxx.portail.ear</groupId>
<artifactId>_xxxEAR</artifactId>
<version>1.0.0-20xxxxx.xxxxx-x</version>
<type>ear</type>
</dependency>
I need to comment single/multiple lines from XML file.
How can i... (6 Replies)
Discussion started by: scorpio
6 Replies
6. Shell Programming and Scripting
Dear All,
I have many cron entries and want to comment a particular cron entry from a script.
Ex- Suppose I have the below cron entries:
# DO NOT EDIT THIS FILE - edit the master and reinstall.
#Cron entries for Jboss server 1
0 23 * * * /usr/bin/echo
0 23 * * * /usr/bin/asdg_count.sh
0 23 *... (5 Replies)
Discussion started by: avishek007
5 Replies
7. Shell Programming and Scripting
Hi
can any body pls help me :
I have a file Which Content is like following:
p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog 2<>/dev/msglog
ca:3:respawn:/opt/GoldWing/currentPM/local/critagt > /dev/msglog 2<>/dev/msglog
ca:3:respawn:/opt/GoldWing/currentPM/local/startcia.sh... (2 Replies)
Discussion started by: Aditya.Gurgaon
2 Replies
8. Shell Programming and Scripting
Hi,
I need to comment the below lines in a file using sed.These are the few lines of the jsp file that need to be commented.
if(top.location != location){
top.location.href = location.href;
}
Using the below command two lines can be commented:
if(top.location != location){
... (9 Replies)
Discussion started by: meetu
9 Replies
9. Shell Programming and Scripting
Hi All,
I am struggling to get my head around the following issue.
I am having to comment out lines between two delimiters by placing an asterix in position 7 but retain all lines in the file and in the same order.
so for example a file containing:
...
...
DELIM1
...
...
DELIM2... (2 Replies)
Discussion started by: Bruble
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
Can anyone let me know how to comment multiple lines in VI editor?
Many thanks.
Regards,
Venkat. (3 Replies)
Discussion started by: venkatesht
3 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)