02-02-2007
I don't disagree with anything you have said, however...
Quote:
Originally Posted by sb008
Based on the fact that was stated that the format of the files is:
filename<date>.dat
the regular expression would be strict enough, since it's fair to assume that whatever program produces these output files produces them with a valid date in the file name.
If you're going to assume that whatever program produces these output files produces them with a valid date in the file name, 1) you've made your regular expression unnecessarily strict; that is, you could have just as easily used filename[0-9][0-9][0-9][0-9][0-9][0-9].dat (although less reasonable, it's certainly easier to type), and 2) you're assuming the original poster's request is irrelevant, since his requirement was to "match the filenames like so, ls filename[01-12][01-31][00-99].dat thus guaranteeing [his] date format".
Quote:
Originally Posted by sb008
If other files are around with a similar format, your regular expression, even though it's more strict, would be as useless as mine. Unless ofcourse you promote the filosophy that a statement is better if it has a smaller chance on producing errors.
In most cases here on unix.com, I do promote that philosophy.
Quote:
Originally Posted by sb008
The only valid option, if files with similar patterns are around, is to isolate the date part from the filename and use e.g. a date conversion command/tool on that pattern and test for the return code.
I agree, and that is something I have considered. However, I don't know of one offhand, and although I could write one, unless you can suggest an existing one to me, I can not offer it.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I would like to process a list of files matching: GPS*\.xyz with an awk script. I would then like to output the files to GPS*\.xyz.out (e.g. the same file name appended with .out). Something like:
awk '{if(NR==1) {offset=-$1}; $1=$1+offset; print }' GPS*.xyz
this does exactly what I want EXCEPT... (3 Replies)
Discussion started by: franzke
3 Replies
2. Shell Programming and Scripting
How can I pass in an argument such as "*.k" to a bash script
without having to double-quote *.k and not having *.k
`glob` to match all files in the pattern?
I tried using noglob in my script but this didn't work the way I thought
it would.. expansion is still occuring, $# is higher than I... (3 Replies)
Discussion started by: zoo591
3 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have a path like this c:\test\sample\programs, i need to change thiis to c:\\test\\sample\\programs. How to perform this? I tried tr command but it didn't help me.
Thanks
Vijayan (3 Replies)
Discussion started by: mvictorvijayan
3 Replies
4. Shell Programming and Scripting
Hi all,
I need to know way of inserting backward slash before forward slash. My problem is that i need to supply directory path as an argument while invoking cshell script. This argument is further used in script (i.e. sed is used to insert this path in some file). So i need to place \ in front... (2 Replies)
Discussion started by: sarbjit
2 Replies
5. Shell Programming and Scripting
Hi guys,
Here is a simple script. It writes the current time to specific files in a directory.
The arguments are the names of the files to write the date to (without path nor extension).
root:~# cat /usr/local/bin/dummy.sh
#!/bin/sh -e
for file in $@; do
date >> /var/lib/$file.dat... (11 Replies)
Discussion started by: chebarbudo
11 Replies
6. UNIX for Dummies Questions & Answers
hi guys,
jus some file globbing questions
sed "s/^.*on//"
what does the full stop and asterisk means?
i onli know that ^ means inverse or not (1 Reply)
Discussion started by: ment0smintz
1 Replies
7. Shell Programming and Scripting
Hello folks!
While "sedding" about again, I ran into this little conundrum du jour:#!/usr/bin/perl
use strict;
use warnings;
use diagnostics;
@ARGV = ('./afile.dat', './*.txt');
$^I = '';
while (<>)
{
s/Twinkies/Dinner/g;
print;
}When run, perl complains,...but, of... (1 Reply)
Discussion started by: LinQ
1 Replies
8. Shell Programming and Scripting
Hello folks!
While "sedding" about again, I ran into this little conundrum du jour:#!/usr/bin/perl
use strict;
use warnings;
use diagnostics;
@ARGV = ('./afile.dat', './*.txt');
$^I = '';
while (<>)
{
s/Twinkies/Dinner/g;
print;
}When run, perl complains,...but, of... (2 Replies)
Discussion started by: LinQ
2 Replies
9. Shell Programming and Scripting
$ ls -1
a.1
b.1
x_a.1
x_b.1
$ ls -1 *
b.1
x_a.1
x_b.1
$ ls -1 **
a.1
b.1
x_a.1
x_b.1The last result is not as expected.
Why?
Thanks. (2 Replies)
Discussion started by: carloszhang
2 Replies
10. Shell Programming and Scripting
Hi ,
I'm facing a different behaviour with one of my shell script for last few days. It was working good before that.
here is my code for the script FileRemove.sh
#get the file name#
file1=$1
file2=$2
rm $file1 # delete the old file
mv $file2 <target path> #move the new file to the target... (5 Replies)
Discussion started by: poova
5 Replies
UNKNOWN(1) General Commands Manual UNKNOWN(1)
NAME
unknown - identify possible genotypes for unknowns
SYNOPSIS
A program to rapidly identify which genotypes are possible for individuals typed as unknowns in the input pedigree.
unknown [ -cl ]
DESCRIPTION
unknown infers possible genotypes and mating combinations for parents with unknown genotypes for ilink(1), mlink(1) and linkmap(1).
OPTIONS
-c Use conditional allele frequencies.
-l Choose a good set of loop breakers automatically.
RETURN VALUE
0 Successful completion
ERRORS
10 File not found
255 Failure
EXAMPLES
Normally, unknown(1) is run immediately prior to its sister programs, ilink(1), mlink(1) and linkmap(1), like this:
unknown
mlink
FILES
unknown(1) reads the two files pedfile.dat and datafile.dat as its own input and produces various temporary files that are used as input to
the next program. These temporary files are ipedfile.dat, upedfile.dat, speedfile.dat and newspeedfile.dat.
NOTES
unknown(1) is part of the FASTLINK package, which is a re-implementation of the LINKAGE suite of computer tools that help investigate
genetic linkage as first proposed G.M. Lathrop, J.M. Lalouel, C. Julier, and J. Ott.
AUTHORS
Dylan Cooper, Alejandro Schaffer, and Tony Schurtz based on work originally by Jurg Ott, Ph.D, et. al.
This manual page was written by Elizabeth Barham <lizzy@soggytrousers.net> for the Debian GNU/Linux system (but may be used by others).
WORD-WIDE-WEB
http://www.ncbi.nlm.nih.gov/CBBResearch/Schaffer/fastlink.html
SEE ALSO
ilink(1), linkmap(1), lodscore(1), mlink(1).
April 15, 2003 UNKNOWN(1)