Sponsored Content
Full Discussion: Grep issue
Top Forums UNIX for Dummies Questions & Answers Grep issue Post 302542729 by Corona688 on Thursday 28th of July 2011 11:48:05 AM
Old 07-28-2011
What is your system? What is your shell?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

issue with grep

using grep, i have a file emp.lst, and i want all those records where "S" or "s" (capital or small) is not there i used this grep emp.lst when i use grep emp.lst i am getting rows with S..but why negate (^) is not working? (3 Replies)
Discussion started by: soujanya_srk
3 Replies

2. UNIX for Dummies Questions & Answers

Issue with grep

I have a file that has the following: 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 591066 100.0 ... (5 Replies)
Discussion started by: Pablo_beezo
5 Replies

3. Shell Programming and Scripting

Grep Issue

<record> <set> <termId>1234</termId> <termType>First</termType> </set> <set> <termId>5678</termId> <termType>Second</termType> </set> </record> This is saved in record.xml Hi I have this sample XML that i am grepping using a shell program. The objective of the task is - based... (7 Replies)
Discussion started by: revertback
7 Replies

4. Shell Programming and Scripting

grep issue

The below command is not working stackmem="$(pmap $1 | grep -i '' | awk '{print $2}'| tr -d ' K')" I need to grep strictly for ----> Regards, Mohtashim (2 Replies)
Discussion started by: mohtashims
2 Replies

5. Shell Programming and Scripting

Grep issue

Hi All I have a file containing following records: $HEW_TGT_DB2_USER=hbme_bi2 $prmAttunityUser=ais $DS_USER=hbme_bi2 $prmStgUser=hbme_bi2 $prmuser=hbme_bi2 $prmStgPass=hbme_bi2 $prmpwd=hbme_bi2 $prmAttunityUser=ais Say suppose the name of the file is test4.txt When i fire this... (2 Replies)
Discussion started by: vee_789
2 Replies

6. Shell Programming and Scripting

Issue in grep

i have following pattern in file s6:s2 s2:s4 s1:s2:s3:s4:s5:s6 s1 . . Now i want to find occurence of each record in file like s6:s2 occurs twice {once in first record and both occur in 3 record as well} so output should be s6:s2 2 s2:s4 2 s1:s2:s3:s4:s5:s6 :1 s1 : 2 ... (7 Replies)
Discussion started by: sharad.40216
7 Replies

7. Shell Programming and Scripting

Grep issue

Hi Guys, I am new to shell scripting. Need help on grep command. I had a file called file.log which contain below statements. 12 Nov 2013 14:12:17,756 INFO security - Userid: raja, Saved File Instance, Name: , Registry: 23 Nov 2013 14:14:11,777 INFO security - Userid: raja, Saved... (7 Replies)
Discussion started by: Vinoth Kumar G
7 Replies

8. UNIX for Dummies Questions & Answers

Grep issue

HI, I have a command to check a license file. License_print. In that file you get the headlines and all different licenses. Now i want to have things extracted from it. so i do like following: license_print | grep -iw -e "user" -e "admin" But i donīt want all lines where user is... (11 Replies)
Discussion started by: Tzwaj
11 Replies

9. Shell Programming and Scripting

Issue with grep

Hello, I have an input file that looks like so: LDLR LDLRAD4 VLDLR when I grep "LDLR" I get an output of: LDLR LDLRAD4 VLDLR Since all names have "LDLR" included within them, but all I want the output to be is LDLR I know it can work if I surround the words with pipes for... (5 Replies)
Discussion started by: Rabu
5 Replies

10. UNIX for Dummies Questions & Answers

Issue with Grep

Hi guys, Hope someone can help me with this - I'm sure it's fairly simple but it's driving me mad! (forgive the coding - still new on scripting - come from Windows) I have the following coding for checking whether I want to include a line in a file:- EXTRACT_Date=$(date --date="${PERIOD}"... (6 Replies)
Discussion started by: NickF
6 Replies
LaCheck(1)						      General Commands Manual							LaCheck(1)

NAME
lacheck - A consistency checker for LaTeX documents. SYNOPSIS
lacheck filename [ .tex ] DESCRIPTION
LaCheck is a general purpose consistency checker for LaTeX documents. It reads a LaTeX document and displays warning messages, if it finds bad sequences. It should be noted, that the badness is very subjective. LaCheck is designed to help find common mistakes in LaTeX docu- ments, especially those made by beginners. The things checked are: Mismatched groups (braces), environments and math mode delimiters. When a mismatch is found, line numbers for both start and end of the mismatch is given. The error messages comes in pairs, one for the end match and one for the beginning, marked with `<-' and `->' respec- tively. Bad spacing including missing a ` ' after an abbreviation, missing an `@' before a punctuation mark in a paragraph that is ended by an capital letter, double spaces like ` ', bad usage of ellipsis (like using ... instead of ldots, or using ldots where cdots should be used), missing before a cite or ef commands, space before footnotes, italic corrections before comma, point, or italic text, italic correction after normal text, missing italic correction when switching from italic to normal text, and double italic correction. Badly placed punctuation marks around end of math mode delimiters. This is, punctuation placed right after display math end or punctuation placed right before text math end. Sequences of whitespace followed by punctuation marks are also caught. Bad use of quotation characters, i.e. constructs like "'word" or "word`" are warned about, tabs in verbatim environments are caught, cer- tain TeX primitives are frowned upon, attempts to give font specifiers arguments such as em{text} are noted, and use of @ in LaTeX macros are reported. LaCheck will read files that are input using input or include. Files with suffix `.sty' are omitted, as they probably will cause LaCheck to crash. LaCheck may be invoked from within Emacs(1) using compile: To run: M-x compile RET lacheck RET , and then C-x ` to parse the messages OUTPUT
The output is UNIX-error like, and may be parsed using Emacs(1) compile mode. Here is a sample: lacheck compiler "/usr/mef/compiler.tex", line 34: missing `\\ ' after "etc." "/usr/mef/compiler.tex", line 179: double space at " ~" "/usr/mef/compiler.tex", line 186: <- unmatched "}" "/usr/mef/compiler.tex", line 181: -> unmatched "$$" A control space ` ' should be inserted at line 34, to prevent an end-of-sentence space. Also, at line 179, the first space of the sequence " ~" should probably be deleted. The last two lines is an example, where the user mistyped, and probably inserted an extra "}" somewhere. DIAGNOSTICS
Some special cases should be explained. In cases where a sentence ends with something that LaCheck thinks is an abbreviation an missing ` ' error may also occur, if the following sentence begins with a lowercase letter. A mismatch error may cause more to follow, due to the chosen algorithm. In such cases just correct the first error and run LaCheck again Braces, environments and math mode must be balanced within a file. LaCheck may be confused by unmatched stuff placed inside verbatim-like environments called something else than exactly `verbatim'. FILES
/usr/bin/lacheck SEE ALSO
tex(1), emacs(1), latex(1) BUGS
LaCheck gets confused by advanced macros, is fooled by simple macros, can't figure out if you use a non-standard way to switch italic on or off, does not like TeX at all, does not provide any options to turn off specific warnings, and is at best a crude approximation. Ideas for improvements and bug reports are very welcome. Such should be directed to the maintainers, their email address is <auc- tex_mgr@sunsite.auc.dk>. AUTHOR
Kresten Krab Thorup with modifications by Per Abrahamsen. Release 1.26 12/25/11 LaCheck(1)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy