02-23-2016
One can also mention these forums
Try, if not posting, solving the problems which occur here.
This will mostly improve your awk/sed/regex understanding, cause nothing beats practice.
Then compare your code to the one who responded before you.
It will probably be much shorter and more efficient (in the start).
Learn from it and try to 'disassemble it'.
A great part of these forums is text parsing and requests to convert data, matching strings, lines before and after and other more or less mundane tasks.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How can i create a regular expression which can detect a new line charcter followed by a special character say * and replace these both by a string of zero length?
Eg:
Input File san.txt
hello
hi ... (6 Replies)
Discussion started by: sandeep_hi
6 Replies
2. Shell Programming and Scripting
Hi,
can anyone advise me how to shorten this:
if || ; then
I tried but it dosent seem to work, whats the correct way.
Cheers (4 Replies)
Discussion started by: jack1981
4 Replies
3. Shell Programming and Scripting
I have following content in the file
CancelPolicyMultiLingual3=U|PC3|EN
RestaurantInfoCode1=U|restID1|1
.....
I am trying to use following matching extression
\|(+)
to get this
PC3|EN
restID1|1
Obviously it does not work.
Any ideas? (13 Replies)
Discussion started by: arushunter
13 Replies
4. UNIX for Dummies Questions & Answers
Hi Gurus,
I need help with regular expressions. I want to create a regular expression which will take only alpha-numeric characters for 7 characters long and will throw out an error if longer than that.
i tried various combinations but couldn't get it, please help me how to get it guys.
... (2 Replies)
Discussion started by: ragha81
2 Replies
5. Shell Programming and Scripting
Hi gurus,
Can any of you suggest any good link for going through tagged regular expressions for unix.I am finding it quite critical and need some help from all gurus to know this better.
Any good link containing detailed examples with descriptions would do i guess.
thanks in advance. (0 Replies)
Discussion started by: navojit dutta
0 Replies
6. Shell Programming and Scripting
Hi,
In ksh, I am trying to compare folder names having -141- in it's name.
e.g.: 4567-141-8098 should match this expression '*-141-*'
but, -141-2354 should fail when compared with '*-141-*'
simlarly, abc should fail when compared with '*-141-*'
I tried multiple things but nevertheless,... (5 Replies)
Discussion started by: jidsh
5 Replies
7. Shell Programming and Scripting
what elements does " /^/ " match?
I did the test which indicates that it matches single lowercase character like 'a','b' etc. and '1','2' etc.
But I really confused with that. Because, "/^abc/" matches strings like "abcedf" or "abcddddee".
So, what does caret ^ really mean?
Any response... (2 Replies)
Discussion started by: DavidHe
2 Replies
8. Shell Programming and Scripting
need a regex that matches when a number has a zero (0) at the end of it
so like
10
20
120
30
330
1000
and so on (6 Replies)
Discussion started by: linuxkid
6 Replies
9. Shell Programming and Scripting
I am new to shell scripts.Can u please help me on this req.
test_user = "Arun"
if
echo "test_user is a word"
else
echo "test_user is not a word" (1 Reply)
Discussion started by: chandrababu
1 Replies
10. Shell Programming and Scripting
Hi
Ilove unix and alwyas trying to to learn unix,but i am weak in using regular expressions.can you please give me a littel brief discription that how can i understand them and how to use .your response could lead a great hand in my unix love. (1 Reply)
Discussion started by: manoj attri
1 Replies
LEARN ABOUT LINUX
licensecheck
LICENSECHECK(1) LICENSECHECK(1)
NAME
licensecheck - simple license checker for source files
SYNOPSIS
licensecheck --help|--version
licensecheck [--no-conf] [--verbose] [--copyright] [-l|--lines=N] [-i|--ignore=regex] [-c|--check=regex] [-m|--machine] [-r|--recursive]
list of files and directories to check
DESCRIPTION
licensecheck attempts to determine the license that applies to each file passed to it, by searching the start of the file for text
belonging to various licenses.
If any of the arguments passed are directories, licensecheck will add the files contained within to the list of files to process.
OPTIONS
--verbose, --no-verbose
Specify whether to output the text being processed from each file before the corresponding license information.
Default is to be quiet.
-l=N, --lines=N
Specify the number of lines of each file's header which should be parsed for license information. (Default is 60).
-i=regex, --ignore=regex
When processing the list of files and directories, the regular expression specified by this option will be used to indicate those which
should not be considered (e.g. backup files, VCS metadata).
-r, --recursive
Specify that the contents of directories should be added recursively.
-c=regex, --check=regex
Specify a pattern against which filenames will be matched in order to decide which files to check the license of.
The default includes common source files.
--copyright
Also display copyright text found within the file
-m, --machine
Display the information in a machine readable way, i.e. in the form <file><tab><license>[<tab><copyright>] so that it can be easily
sorted and/or filtered, e.g. with the awk and sort commands. Note that using the --verbose option will kill the readability.
--no-conf, --noconf
Do not read any configuration files. This can only be used as the first option given on the command-line.
CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables.
Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The
currently recognised variables are:
LICENSECHECK_VERBOSE
If this is set to yes, then it is the same as the --verbose command line parameter being used. The default is no.
LICENSECHECK_PARSELINES
If this is set to a positive number then the specified number of lines at the start of each file will be read whilst attempting to
determine the license(s) in use. This is equivalent to the --lines command line option.
LICENSE
This code is copyright by Adam D. Barratt <adam@adam-barratt.org.uk>, all rights reserved; based on a script of the same name from the KDE
SDK, which is copyright by <dfaure@kde.org>. This program comes with ABSOLUTELY NO WARRANTY. You are free to redistribute this code under
the terms of the GNU General Public License, version 2 or later.
AUTHOR
Adam D. Barratt <adam@adam-barratt.org.uk>
Debian Utilities 2013-12-23 LICENSECHECK(1)