09-13-2004
I think having the "#" character there is dodgy because the shell is probably treating the end of the filename as a comment.
I'd also advise against using a "?" as a "regular" character, seeing as it's a shell wildcard - that will end up causing problems somewhere down the line too. Use an underscore instead.
Cheers
ZB
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi - I am trying to ignore the following items from a list.
lp0
lp11
lp12
lp14
The following code works fine, but I was wondering if there was a tidier way to write the lp regular expression?
egrep -v "lp"
Thanks in advance. (3 Replies)
Discussion started by: Krispy
3 Replies
2. Shell Programming and Scripting
:confused:
Is there any way to use in awk a regular exprexion with a format not previusly known?
I mean something like /VAR/ ,obviously VAR is the variable exprexion.
Thak you all in advance. (4 Replies)
Discussion started by: Klashxx
4 Replies
3. Shell Programming and Scripting
hi
i need to wipe out something from giving path i have some thing like that :
pwd | sed 's/.*foo//'
it is working fine when I have path like : /blah/balh1/foo/moo
so it erasing me all that comes before the foo including the foo
but I have problem when I have dir by the name of... (7 Replies)
Discussion started by: umen
7 Replies
4. UNIX for Dummies Questions & Answers
Folks;
Could some one tell me what these 2 regular expressions mean:
*/(*)/*
(\d\d\d\d/\d\d/\d\d/*?) (14 Replies)
Discussion started by: Katkota
14 Replies
5. Shell Programming and Scripting
Hi All,
Is my script still error??
i try to running and still error??
need help (1 Reply)
Discussion started by: justbow
1 Replies
6. Shell Programming and Scripting
Here's my script
read number
if echo $number | grep ""
I want this "if" statement to return true only when numbers without letters is matched.
For example 45 - true, 923 - true, r5 - false, tg/f - false and so on.
In this script even a single digit number like "3" returns false.
Thanks. (1 Reply)
Discussion started by: eXPlosion
1 Replies
7. Shell Programming and Scripting
Hi,
I would like to know if the parameter i am passing to a shell script is contain
the following charachter : ASM.
I belive that i should use regular expresion here.
Can one help ?
Bellow is the "if statment" i need to fix with the reg exp:
if ; then
#echo "IT IS AN RDBMS... (4 Replies)
Discussion started by: yoavbe
4 Replies
8. Shell Programming and Scripting
Hi
I have a multiple line file in the following format:
....
1095 1000 0011 0000 1000 0101 0100 1100 1111
1096 1000 0011 0000 1000 0101 0100 1100 1111
1111 1000 0011 0010 1000 1001 0100 1100 1101
1112 1000 0011 0000 1000 0001 0100 1100 ... (11 Replies)
Discussion started by: aoussenko
11 Replies
9. Shell Programming and Scripting
my $hw_plf_desc = `grep hw_platform $NODE_CFG_FILE`;
if($hw_plf_desc =~ /Netra X4270 X4446A M2 /)
Could someone explain the use of =~ .... this works only for perl . What is the alternate for the same in shell . Could any one convert this to shell script (7 Replies)
Discussion started by: frintocf
7 Replies
10. Shell Programming and Scripting
Hi,
I am getting a string in the file, I want to parse the srting and extract the percentage from the string. Sample string are -
ASAD112_sd12.34%adnmfk
ASAsds_1.34%adnmfk
ASAdf 2 sd12.34%adnmfk
ASAD112_sd 12.34% adnmfk
ASAD112_sd12.34% adnmfk
I want to extract the numeric value... (3 Replies)
Discussion started by: meetvipin
3 Replies
LEARN ABOUT XFREE86
git-stripspace
GIT-STRIPSPACE(1) Git Manual GIT-STRIPSPACE(1)
NAME
git-stripspace - Remove unnecessary whitespace
SYNOPSIS
git stripspace [-s | --strip-comments]
git stripspace [-c | --comment-lines]
DESCRIPTION
Read text, such as commit messages, notes, tags and branch descriptions, from the standard input and clean it in the manner used by Git.
With no arguments, this will:
o remove trailing whitespace from all lines
o collapse multiple consecutive empty lines into one empty line
o remove empty lines from the beginning and end of the input
o add a missing
to the last line if necessary.
In the case where the input consists entirely of whitespace characters, no output will be produced.
NOTE: This is intended for cleaning metadata, prefer the --whitespace=fix mode of git-apply(1) for correcting whitespace of patches or
files in the repository.
OPTIONS
-s, --strip-comments
Skip and remove all lines starting with comment character (default #).
-c, --comment-lines
Prepend comment character and blank to each line. Lines will automatically be terminated with a newline. On empty lines, only the
comment character will be prepended.
EXAMPLES
Given the following noisy input with $ indicating the end of a line:
|A brief introduction $
| $
|$
|A new paragraph$
|# with a commented-out line $
|explaining lots of stuff.$
|$
|# An old paragraph, also commented-out. $
| $
|The end.$
| $
Use git stripspace with no arguments to obtain:
|A brief introduction$
|$
|A new paragraph$
|# with a commented-out line$
|explaining lots of stuff.$
|$
|# An old paragraph, also commented-out.$
|$
|The end.$
Use git stripspace --strip-comments to obtain:
|A brief introduction$
|$
|A new paragraph$
|explaining lots of stuff.$
|$
|The end.$
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-STRIPSPACE(1)