The "problem" is the way parameter expansion is done. Example:
Spot the difference? In the first example, echo is passed 6 parameters (split on the whitespaces), and by default it outputs them using one whitespace as separator. In the second example, the variable is passed as one parameter, whitespaces and all.
Hello,
I want to compare two files. All records in file 2 that are not in file 1 should be output to file 3.
For example:
file 1
123
1234
123456
file 2
123
2345
23456
file 3 should have
2345
23456
I have looked at diff, bdiff, cmp, comm, diff3 without any luck! (2 Replies)
I am trying to check to see if a file exists on a ftp server, well, I know that cant be done, atleast directly, So I came up with this small script
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
cd public_html/crap
dir $FILE
quit
END_SCRIPT
Where the $ variable... (2 Replies)
Hi List,
How to read the output of a command executed from a script.
For ex.
sample_scritp.sh
-------------
useradd testuser1
password testuser1
....
.....
--------------
This prompts for "password", and "confirm password", for which i need to give the values from script.
Can... (4 Replies)
hi,
i have a script which pipes the output of a diff -rq command into a separate file/ it would read something like this:
Files mod1/lala/xml/test1.txt and mod2/lala/xml/test1.txt differ
Only in mod2/lala/xml: test2.txt
What i need to do is to parse this file so i end up with just a... (5 Replies)
Hello, in a script i would like to evaluate a command output with a grep, for example, to know if the parameter defined by the user is in the output.
Something like: the_command | grep $1
Please, how is the way to evalulate in this a script, like
if
echo "incorrect parameter, not in... (2 Replies)
I have written shell script to send file as an attachemt of email and output of "top -o res" command as email body. it works fine if i execute manually from prompt but it does not send "top -o res" command output in email body when it is executed via crontab. Any suggestions. My script is below:... (5 Replies)
Hi
I would like to write a shell script which replace particular text in output of a shell command. For example : If I execute pwd (if dir is /users/master/) it should display as - /users/Master_directory/.
Also, for generalising the script I would like to receive parameters when I run the... (3 Replies)
Hi Team,
Need a help on how to pipe a command out put to a shell script. My shell script looks like below.
cat shell_script
#!/usr/bin/ksh
input =$@
echo " we are inside the shell script"
echo " here are the input parameters"
..........................
..................
... (11 Replies)
Hi ,
Can some one help me how to pass ls command output to diff command
ex : - ls *.xml will return files which have time stamps
abc-<time-stamp>.xml
xyz-<time-stamp>.xml
diff abc-<time-stamp>.xml xyz-<time-stamp>.xml >> newfile.txt
we need to... (9 Replies)
Discussion started by: techie_09
9 Replies
LEARN ABOUT DEBIAN
test::eol
Test::EOL(3pm) User Contributed Perl Documentation Test::EOL(3pm)NAME
Test::EOL - Check the correct line endings in your project
SYNOPSIS
"Test::EOL" lets you check for the presence of trailing whitespace and/or windows line endings in your perl code. It reports its results in
standard "Test::Simple" fashion:
use Test::EOL tests => 1;
eol_unix_ok( 'lib/Module.pm', 'Module is ^M free');
and to add checks for trailing whitespace:
use Test::EOL tests => 1;
eol_unix_ok( 'lib/Module.pm', 'Module is ^M and trailing whitespace free', { trailing_whitespace => 1 });
Module authors can include the following in a t/eol.t and have "Test::EOL" automatically find and check all perl files in a module
distribution:
use Test::EOL;
all_perl_files_ok();
or
use Test::EOL;
all_perl_files_ok( @mydirs );
and if authors would like to check for trailing whitespace:
use Test::EOL;
all_perl_files_ok({ trailing_whitespace => 1 });
or
use Test::EOL;
all_perl_files_ok({ trailing_whitespace => 1 }, @mydirs );
DESCRIPTION
This module scans your project/distribution for any perl files (scripts, modules, etc) for the presence of windows line endings.
FUNCTIONS
all_perl_files_ok
all_perl_files_ok( [ \%options ], [ @directories ] )
Applies "eol_unix_ok()" to all perl files found in @directories (and sub directories). If no <@directories> is given, the starting point is
one level above the current running script, that should cover all the files of a typical CPAN distribution. A perl file is *.pl or *.pm or
*.t or a file starting with "#!...perl"
Valid "\%options" currently are:
o trailing_whitespace
By default Test::EOL only looks for Windows (CR/LF) line-endings. Set this to true to raise errors if any kind of trailing whitespace
is present in the file.
o all_reasons
Normally Test::EOL reports only the first error in every file (given that a text file originated on Windows will fail every single
line). Set this a true value to register a test failure for every line with an error.
If the test plan is defined:
use Test::EOL tests => 3;
all_perl_files_ok();
the total number of files tested must be specified.
eol_unix_ok
eol_unix_ok ( $file [, $text] [, \%options ] )
Run a unix EOL check on $file. For a module, the path (lib/My/Module.pm) or the name (My::Module) can be both used. $text is the diagnostic
label emited after the "ok"/"not ok" TAP output. "\%options" takes the same values as described in "all_perl_files_ok".
EXPORT
A list of functions that can be exported. You can delete this section if you don't export anything, such as for a purely object-oriented
module.
ACKNOWLEDGEMENTS
Shamelessly ripped off from Test::NoTabs.
SEE ALSO
Test::More, Test::Pod. Test::Distribution, <Test:NoWarnings>, Test::NoTabs, Module::Install::AuthorTests.
AUTHORS
o Arthur Axel 'fREW' Schmidt <frioux@gmail.com>
o Florian Ragwitz <rafl@debian.org>
o Kent Fredric <kentfredric@gmail.com>
o Peter Rabbitson <ribasushi@cpan.org>
o Tomas Doran <bobtfish@bobtfish.net>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Tomas Doran.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-06-15 Test::EOL(3pm)