What is the correct format for a single command that would combine portions of 2 different lines in the command history? I'm using a C shell. Here's a simplified command history to clarify:
4 rm file1
5 ls -ld file2 file3 file4
6 cat file 5
With the above history, what would be the... (5 Replies)
Dear Experts
I am trying to find if it is possible to combine unix commands in awk program. For example if it is possible embed rm or ls or any unix command inside the awk program and while it is reading the file besides printing be able to do some unix commands. I am thinking may be just print... (2 Replies)
I would like to change the lines:
originalline1
originalline2
to:
originalline1new
originalline1newline
originalline2new
originalline2newline
To do this, id like to combine the commands:
sed 's/^/&new/g' file > newfile1
and
sed '/^/ a\\
newline\\
\\ (2 Replies)
Hello all,
I am trying to list and count all the files of a particular type in any given directory. I can use the commands separately but when I combine them they do not give an output.
The command for counting the files is ls -1 | wc -l and for listing all the file of particular type say... (2 Replies)
Is there anyway to achieve "find /home -name "*.bashrc" 2>/dev/null" and "PS1="\n>"" in the same command? I just wanna add a line to the previous command to change the PS1 variable to ">". (1 Reply)
Hi Guys,
I am looking to optimze these 5 SSH lines to a single SSH to get my machine to not hang! lol!
cat hosts.lst | xargs -n1 -t -i echo 'home/util/timeout 6 0 ssh -q {} top -b > util/{}.top &' >> r_query_info
cat hosts.lst | xargs -n1 -t -i echo 'home/util/timeout 6 0 ssh -q {} uname -r... (5 Replies)
hey can anyone tell me how can i combine these two commands so that it is executed only once, but gives me both the results.
IDLE=`sar 30 6 | grep Average | awk '{print $1 $5}' `
sar 30 120 | awk '{print $1" "$5}' >> mailx -m -s "$MSG" xyz@abc.com. (5 Replies)
Hi,
I have a directory with some XML files in it. I can use wildcards to get the list of XMLs I want
say I have following XMLs in same dir
Employee1.xml
Employee2.xml
Employee3.xml
and
Salary1.xml
Salary2.xml
Salary3.xml
apart from other .txt .dat files etc
I want to write a unix... (7 Replies)
I have a directory of 3000 files without extensions (Solaris 5.10).
I would like to iterate the file names through the 'file' command and output their mime types (most are pdf or jpg, but a very few might be psd or swf which show simply as 'data')
So, I would like the output of the 'ls'... (2 Replies)
I can achieve two tasks with 2 different awk commands:
1) awk -F";;WORD" '{print $2}' file | sed '/^$/d' #to find surface_word
2) awk -F"bw:|gloss:" '// {print $2}' file | sed '/\//!d; s:/*+*: + :g; s:^+::; s: *+ *$::;' #to find segmentation of surface_word
Number 1) finds surface_word... (7 Replies)
Discussion started by: Viernes
7 Replies
LEARN ABOUT DEBIAN
email::send::test
Email::Send::Test(3pm) User Contributed Perl Documentation Email::Send::Test(3pm)NAME
Email::Send::Test - Captures emails sent via Email::Send for testing
SYNOPSIS
# Load as normal
use Email::Send;
use Email::Send::Test;
# Always clear the email trap before each test to prevent unexpected
# results, and thus spurious test results.
Email::Send::Test->clear;
### BEGIN YOUR CODE TO BE TESTED (example follows)
my $sender = Email::Send->new({ mailer => 'Test' });
$sender->send( $message );
### END YOUR CODE TO BE TESTED
# Check that the number and type (and content) of mails
# matched what you expect.
my @emails = Email::Send::Test->emails;
is( scalar(@emails), 1, 'Sent 1 email' );
isa_ok( $emails[0], 'Email::MIME' ); # Email::Simple subclasses pass through
DESCRIPTION
Email::Send::Test is a driver for use in testing applications that use Email::Send to send email.
To be able to use it in testing, you will need some sort of configuration mechanism to specify the delivery method to be used, or some
other way that in your testing scripts you can convince your code to use "Test" as the mailer, rather than "Sendmail" or another real
mailer.
How does it Work
Email::Send::Test is a trap for emails. When an email is sent, it adds the emails to an internal array without doing anything at all to
them, and returns success to the caller.
If your application sends one email, there will be one in the trap. If you send 20, there will be 20, and so on.
A typical test will involve doing running some code that should result in an email being sent, and then checking in the trap to see if the
code did actually send out the email.
If you want you can get the emails out the trap and examine them. If you only care that something got sent you can simply clear the trap
and move on to your next test.
The Email Trap
The email trap is a simple array fills with whatever is sent.
When you send an email, it is pushed onto the end of the array. You can access the array directly if you wish, or use the methods provided.
METHODS
send $message
As for every other Email::Send mailer, "send" takes the message to be sent.
However, in our case there are no arguments of any value to us, and so they are ignored.
It is worth nothing that we do NOTHING to check or alter the email. For example, if we are passed "undef" it ends up as is in the trap. In
this manner, you can see exactly what was sent without any possible tampering on the part of the testing mailer.
Of course, this doesn't prevent any tampering by Email::Send itself :)
Always returns true.
emails
The "emails" method is the preferred and recommended method of getting access to the email trap.
In list context, returns the content of the trap array as a list.
In scalar context, returns the number of items in the trap.
clear
The "clear" method resets the trap, emptying it.
It is recommended you always clear the trap before each test to ensure any existing emails are removed and don't create a spurious test
result.
Always returns true.
deliveries
This method returns a list of arrayrefs, one for each call to "send" that has been made. Each arrayref is in the form:
[ $mailer, $email, @rest ]
The first element is the invocant on which "send" was called. The second is the email that was given to "send". The third is the rest of
the arguments given to "send".
SUPPORT
All bugs should be filed via the CPAN bug tracker at
http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test>
For other issues, or commercial enhancement or support, contact the author.
AUTHORS
Current maintainer: Ricardo SIGNES, <rjbs@cpan.org>.
Original author: Adam Kennedy <cpan@ali.as>, <http://ali.as/>
COPYRIGHT
Copyright (c) 2004 - 2005 Adam Kennedy. All rights reserved. This program is free software; you can redistribute it and/or modify it under
the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.
perl v5.12.4 2011-08-31 Email::Send::Test(3pm)