03-05-2013
But you hardcoded version 1.0 in there. What if it's 2.3.4? Although the parameter expansion supports nested vars, like ${i/foo/${bar}}, you have to grab the version somehow.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I need to replace automatically all special characters of one filename with some corresponding characters
For example >
ö --> oe
ä --> ae
....
If the special character comes more than one time, then all the coccuerences have to be replaced.
I would like to have a... (6 Replies)
Discussion started by: MAKY
6 Replies
2. Shell Programming and Scripting
Hi,
I have a file like this:
mgr1.dbf
tool.dbf
usr.dbf
wow19.dbf
wow2wow.dbf
Can anyone help change the format after each line of reading to:
mgr2.dbf # add 1 of *1.dbf
tool2.dbf # if not a number exist, make it default to 2
usr2.dbf
wow20.dbf # add 1 of *19.dbf
wow3wow.dbf ... (5 Replies)
Discussion started by: netbanker
5 Replies
3. UNIX for Dummies Questions & Answers
Hi,
If I have a directory full of say 100 random files, and I would like to organize them, for example: FILE001, FILE002, FILE003, FILE004, etc.
How would I do this from Terminal, instead of manually changing each file? I'm using Mac OS X, if that makes a difference.
Thank you in advance... (8 Replies)
Discussion started by: andou
8 Replies
4. Shell Programming and Scripting
Hello,
I have some files in a directory like:
01_07_2010_aa.txt
01_07_2010_bb.txt
01_07_2010_cc.txt
01_07_2010_dd.txt
01_07_2010_ee.txt
01_07_2010_ff.txt
I want to change their names to :
3nm_aa.txt
3nm_bb.txt
3nm_cc.txt
3nm_dd.txt
3nm_ee.txt
3nm_ff.txt (8 Replies)
Discussion started by: ad23
8 Replies
5. Shell Programming and Scripting
Hi is it possible to change multiple files (~10k) names with out disturbing the data in it. ?
input
Hynda|cgr10(+):100027702-1000312480|.txt
Hynda|cgr10(+):100027702-1000312483|.txt
Hynda|cgr10(+):100027702-1000312484|.txt
Hynda|cgr10(+):100027702-1000312482|.txt
output... (4 Replies)
Discussion started by: quincyjones
4 Replies
6. Shell Programming and Scripting
I have 84 files with the following names splitseqs.1, spliseqs.2 etc.
and I want to change the .number to a unique filename.
E.g.
change splitseqs.1 into splitseqs.7114_1#24
and
change spliseqs.2 into splitseqs.7067_2#4
So all the current file names are unique, so are the new file names.... (1 Reply)
Discussion started by: avonm
1 Replies
7. Red Hat
admin.campaign.sql
admin.cardnumber_filter.sql
understand that rename is using mv command but how do I rename such that it become the following:
campaign.sql
cardnumber_filter.sql
thanks (2 Replies)
Discussion started by: jediwannabe
2 Replies
8. UNIX for Dummies Questions & Answers
I have fasta files with multiple sequences in each. I need to change the sequence name headers from:
>accD:_59176-60699
ATGGAAAAGTGGAGGATTTATTCGTTTCAGAAGGAGTTCGAACGCA
>atpA_(reverse_strand):_showing_revcomp_of_10525-12048
ATGGTAACCATTCAAGCCGACGAAATTAGTAATCTTATCCGGGAAC... (2 Replies)
Discussion started by: tyrianthinae
2 Replies
9. Shell Programming and Scripting
Hi,
I have a files in a directory as below :-
ls -1
mqdepth-S1STC02
proc-mq-S1STC01
proc-mq-S1STC02
proc-mq-S1STC03
Whereever i have S1STC i need to copy them into new file with file name S2STC.
expected output :-
ls -1
mqdepth-S2STC02
proc-mq-S2STC01
proc-mq-S2STC02... (3 Replies)
Discussion started by: satishmallidi
3 Replies
10. Shell Programming and Scripting
I have a landing directory on my unix (solaris) server, that receives the following files:
MLH4301I AAOT-hhslog.610.20150805.txt
MLH4301I AAOT-hhslog.611.20150805.txt
MLH4301I AAOT-hhslog.612.20150805.txt
MLH4301I AAOT-hhslog.613.20150805.txt
and I need to add to this files the number 10000... (6 Replies)
Discussion started by: fretagi
6 Replies
LEARN ABOUT MOJAVE
strict
strict(3pm) Perl Programmers Reference Guide strict(3pm)
NAME
strict - Perl pragma to restrict unsafe constructs
SYNOPSIS
use strict;
use strict "vars";
use strict "refs";
use strict "subs";
use strict;
no strict "vars";
DESCRIPTION
If no import list is supplied, all possible restrictions are assumed. (This is the safest mode to operate in, but is sometimes too strict
for casual programming.) Currently, there are three possible things to be strict about: "subs", "vars", and "refs".
"strict refs"
This generates a runtime error if you use symbolic references (see perlref).
use strict 'refs';
$ref = $foo;
print $$ref; # ok
$ref = "foo";
print $$ref; # runtime error; normally ok
$file = "STDOUT";
print $file "Hi!"; # error; note: no comma after $file
There is one exception to this rule:
$bar = &{'foo'};
&$bar;
is allowed so that "goto &$AUTOLOAD" would not break under stricture.
"strict vars"
This generates a compile-time error if you access a variable that was neither explicitly declared (using any of "my", "our", "state",
or "use vars") nor fully qualified. (Because this is to avoid variable suicide problems and subtle dynamic scoping issues, a merely
"local" variable isn't good enough.) See "my" in perlfunc, "our" in perlfunc, "state" in perlfunc, "local" in perlfunc, and vars.
use strict 'vars';
$X::foo = 1; # ok, fully qualified
my $foo = 10; # ok, my() var
local $baz = 9; # blows up, $baz not declared before
package Cinna;
our $bar; # Declares $bar in current package
$bar = 'HgS'; # ok, global declared via pragma
The local() generated a compile-time error because you just touched a global name without fully qualifying it.
Because of their special use by sort(), the variables $a and $b are exempted from this check.
"strict subs"
This disables the poetry optimization, generating a compile-time error if you try to use a bareword identifier that's not a
subroutine, unless it is a simple identifier (no colons) and that it appears in curly braces or on the left hand side of the "=>"
symbol.
use strict 'subs';
$SIG{PIPE} = Plumber; # blows up
$SIG{PIPE} = "Plumber"; # just fine: quoted string is always ok
$SIG{PIPE} = &Plumber; # preferred form
See "Pragmatic Modules" in perlmodlib.
HISTORY
"strict 'subs'", with Perl 5.6.1, erroneously permitted to use an unquoted compound identifier (e.g. "Foo::Bar") as a hash key (before "=>"
or inside curlies), but without forcing it always to a literal string.
Starting with Perl 5.8.1 strict is strict about its restrictions: if unknown restrictions are used, the strict pragma will abort with
Unknown 'strict' tag(s) '...'
As of version 1.04 (Perl 5.10), strict verifies that it is used as "strict" to avoid the dreaded Strict trap on case insensitive file
systems.
perl v5.18.2 2014-01-06 strict(3pm)