File lines starts with # not processed or exclude that lines
I have requirement in my every files starting lines have # needs to be not processing or exclude the that lines.
I have written a code like below, but now working as expected getting ERROR" line 60: [egrep: command not found"
Please suggest me how can i over come this.
Last edited by Don Cragun; 06-20-2014 at 05:26 AM..
Reason: Add CODE tags.
I have a log file that I am processing. This contains messages from and to a server (requests and responses).
The responses to requests may not be in order i.e. we can have a response to a request after several requests are sent, and in some error cases there may not be any response message.
... (2 Replies)
I use while do - done loop in my shell script. It is working as per my expectations.
But I do not want to process all the lines. I am finding it difficult to exclude certain lines.
1) I do not want to process blank lines as well as lines those start with a space " "
2) I do not want to... (2 Replies)
How can I delete those lines that starts with a certain letter?
abc def ghi
xyz abc def
ace gik moq
abe imq gxm
I want to delete the line that starts with "x". Thanks! (4 Replies)
hiiiii
$ grep ^"#" $file
Will give the lines , which starts with # .And I wanna get the lines which are not starting with #.
How to implement that.
Thanking you
Krish:b: (10 Replies)
Hi Guys,
I have an awk script that would search the input file for line that starts with a number 3 and copies into a new text file.
I want to extend this script to find the lines that either starts with 3 or a or b and copy all those lines into the new file.
Here is what I have so far:... (1 Reply)
Hi, I have one file, I need to check if file exist or not and then remove the lines which starts with ?
My file1.out data is some thing
abcabcppp
xyzxyzpqr
?????????
?????????
Output should be in test.out
abcabcppp
xyzxyzpqr
I am getting the output as below but the File does not exist... (4 Replies)
/bin/sed -n ';4757335,$ p' | wc -l
/bin/sed -n ';4757335,$ p' | egrep "Failed" | egrep -c "PM late arrrival"
how can i combine the above two sed commands into one? i want to count the number of lines between the specified line number and the end of the file. AND and i want to count how many... (5 Replies)
I have a file like below
#Fields section bald
1234 2345 456 222
abcs dddd dddd ssss
mmmm mmm mmm
i need do not process a files stating with #
I was written code below
while read -r line
do
if
then
echo ${line} >>
elif
then
... (3 Replies)
Hi
I have a txt file and I would like to use egrep without using -v option to exclude the lines which matches with multiple Strings.
Let's say I have some text in the txt file. The command should not fetch lines if they have strings something like
CAT MAT DAT
The command should fetch me... (4 Replies)
Discussion started by: Sathwik
4 Replies
LEARN ABOUT SUNOS
xgettext
xgettext(1) User Commands xgettext(1)NAME
xgettext - extract gettext call strings from C programs
SYNOPSIS
xgettext [-ns] [ -a [-x exclude-file]] [-c comment-tag] [-d default-domain] [-j] [-m prefix] [-M suffix] [-p pathname] -| filename...
xgettext -h
DESCRIPTION
The xgettext utility is used to automate the creation of portable message files (.po). A .po file contains copies of "C" strings that are
found in ANSI C source code in filename or the standard input if `-' is specified on the command line. The .po file can be used as input
to the msgfmt(1) utility, which produces a binary form of the message file that can be used by application during run-time.
xgettext writes msgid strings from gettext(3C) calls in filename to the default output file messages.po. The default output file name can
be changed by -d option. msgid strings in dgettext() calls are written to the output file domainname.po where domainname is the first
parameter to the dgettext() call.
By default, xgettext creates a .po file in the current working directory, and each entry is in the same order that the strings are
extracted from filenames. When the -p option is specified, the .po file is created in the pathname directory. An existing .po file is
overwritten.
Duplicate msgids are written to the .po file as comment lines. When the -s option is specified, the .po is sorted by the msgid string,
and all duplicated msgids are removed. All msgstr directives in the .po file are empty unless the -m option is used.
OPTIONS
The following options are supported:
-n Add comment lines to the output file indicating file name and line number in the source file where each extracted
string is encountered. These lines appear before each msgid in the following format:
# # File: filename, line: line-number
-s Generate output sorted by msgids with all duplicate msgids removed.
-a Extract all strings, not just those found in gettext(3C), and dgettext() () calls. Only one .po file is created.
-c comment-tag The comment block beginning with comment-tag as the first token of the comment block is added to the output .po
file as # delimited comments. For multiple domains, xgettext directs comments and messages to the prevailing text
domain.
-d default-domain Rename default output file from messages.po to default-domain .po.
-j Join messages with existing message files. If a .po file does not exist, it is created. If a .po file does exist,
new messages are appended. Any duplicate msgids are commented out in the resulting .po file. Domain directives in
the existing .po file are ignored. Results not guaranteed if the existing message file has been edited.
-m prefix Fill in the msgstr with prefix. This is useful for debugging purposes. To make msgstr identical to msgid, use an
empty string ("") for prefix.
-M suffix Fill in the msgstr with suffix. This is useful for debugging purposes.
-p pathname Specify the directory where the output files will be placed. This option overrides the current working directory.
-x exclude-file Specify a .po file that contains a list of msgids that are not to be extracted from the input files. The format of
exclude-file is identical to the .po file. However, only the msgid directive line in exclude-file is used. All
other lines are simply ignored. The -x option can only be used with the -a option.
-h Print a help message on the standard output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWloc |
+-----------------------------+-----------------------------+
SEE ALSO msgfmt(1), gettext(3C), attributes(5)NOTES
xgettext is not able to extract cast strings, for example ANSI C casts of literal strings to (const char *). This is unnecessary anyway,
since the prototypes in <libintl.h> already specify this type.
In messages and translation notes, lines greater than 2048 characters are truncated to 2048 characters and a warning message is printed to
stderr.
SunOS 5.10 23 Mar 1999 xgettext(1)