Sponsored Content
Full Discussion: egrep and Arg list too long
Top Forums UNIX for Dummies Questions & Answers egrep and Arg list too long Post 21711 by azbatz on Tuesday 21st of May 2002 06:32:35 PM
Old 05-21-2002
Re: xargs is COOL!!!

Quote:
Originally posted by Kelam_Magnus
Actually you need to use xargs.

egrep -i -e "string1" -e "string2" *| xargs

Do a man on the details.

Basically, it negates the "arg list too long" message.


Smilie
Hi,
I am trying to do something similar, but I need
to get the results ONLY with matching BOTH search
patterns. When I did the above example I got
results with both patterns AND with either pattern.

For example, I only want to find "date" and "Finished"
and maybe another string from a text file not just "date"
or just "Finished"...

Thanks in Advance!Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

arg list too long

I do ls -l ABC*, I get arg list too long message. This will not happen if ABC* has small no of files I believe 4000 files is limit. Any way of avoiding this. I even tried like this for i in `ls -l ABC*` do echo $i done Same problem. Any solution would be great. I am on HP-UX... (5 Replies)
Discussion started by: vingupta
5 Replies

2. UNIX for Dummies Questions & Answers

zcat --> Arg list too long

Hi all I have more than 1000 files in a folder and when ever i use a "compress" or "zcat" command it give error /bin/zcat: Arg list too long. . any solution for this :o (3 Replies)
Discussion started by: muneebr
3 Replies

3. UNIX for Advanced & Expert Users

arg list too long

Does anyone have a solution for arg list too long error. I have got this from the web but I fail to make any sense out of it Thanks enc (8 Replies)
Discussion started by: encrypted
8 Replies

4. UNIX for Dummies Questions & Answers

ls -t arg list too long

echo dirname/filename* | xargs ls -t As a substitute doesn't give the results desired when I exceed the buffer size. I still want the files listed in chronological order, unfortunately xargs releases the names piecemeal...does anyone have any ideas? :( (4 Replies)
Discussion started by: CSU_Ram
4 Replies

5. UNIX for Dummies Questions & Answers

execvp:ar:Arg list too long -> while linking

I get this error : execvp:ar:Arg list too long when i am trying to link the .obj files created on unix box. Any resolution to this? Thanks Mohit (1 Reply)
Discussion started by: mohitp
1 Replies

6. UNIX for Dummies Questions & Answers

arg list too long when mv files?

hello all i need some help because i am a unix/linux dummy...i have the following: DIR1> has 121437 files in it with varying dates going back to early April, a sub dir DIR1/DIR2> has 55835 files in it I need to move all files (T*.*) out of DIR1 into DIR2 that are older than today? Ive been... (2 Replies)
Discussion started by: jamos007
2 Replies

7. UNIX for Dummies Questions & Answers

Arg List too Long in SCP

Hey guys. I have a program written in which i am trying to get the files from one remote machine and transferring the files to another remote machine using SCP. It works fine for 50 or 60 files but when the files grows to 250 then i get an error message stating "Arg list too long". #scp -p... (5 Replies)
Discussion started by: chris1234
5 Replies

8. Shell Programming and Scripting

arg list too long

Hi, Help. I have a file that contains a list of users in a file. I want to cat the content of the file and feed it into sed to a preformated report. The error I got is "ksh: /usr/bin/sed: arg list too long" My method below. A=`cat FILE1.txt` B=`echo $A` sed "s#USERLIST#$B#" FILE2 >... (2 Replies)
Discussion started by: Zenwork
2 Replies

9. Shell Programming and Scripting

arg list too long error

Hello, I'm trying to search through 30,000 files in 1 directory, and am getting the "arg list too long" error. I've searched this forum and have been playing around with xargs and can't get that to work either. I'm using ksh on Solaris. Here's my original code: nawk "/Nov 21/{_=2}_&&_--"... (14 Replies)
Discussion started by: Kristin_in_CO
14 Replies

10. UNIX for Dummies Questions & Answers

Arg list too long

Hello All, I am trying to find a file name with .sh exention from a list of .dat files inside a directory. find /app/folder1/* -name '*.dat'| xargs grep '.sh' ksh: /usr/local/bin/find: arg list too long Please help me finding the command. Thanks (3 Replies)
Discussion started by: tkhan9
3 Replies
NOTMUCH-SEARCH(1)					      General Commands Manual						 NOTMUCH-SEARCH(1)

NAME
notmuch-search - Search for messages matching the given search terms. SYNOPSIS
notmuch search [options...] <search-term>... DESCRIPTION
Search for messages matching the given search terms, and display as results the threads containing the matched messages. The output consists of one line per thread, giving a thread ID, the date of the newest (or oldest, depending on the sort option) matched message in the thread, the number of matched messages and total messages in the thread, the names of all participants in the thread, and the subject of the newest (or oldest) message. See notmuch-search-terms(7) for details of the supported syntax for <search-terms>. Supported options for search include --format=(json|text) Presents the results in either JSON or plain-text (default). --output=(summary|threads|messages|files|tags) summary Output a summary of each thread with any message matching the search terms. The summary includes the thread ID, date, the num- ber of messages in the thread (both the number matched and the total number), the authors of the thread and the subject. threads Output the thread IDs of all threads with any message matching the search terms, either one per line (--format=text) or as a JSON array (--format=json). messages Output the message IDs of all messages matching the search terms, either one per line (--format=text) or as a JSON array (--format=json). files Output the filenames of all messages matching the search terms, either one per line (--format=text) or as a JSON array (--for- mat=json). tags Output all tags that appear on any message matching the search terms, either one per line (--format=text) or as a JSON array (--format=json). --sort=(newest-first|oldest-first) This option can be used to present results in either chronological order (oldest-first) or reverse chronological order (new- est-first). Note: The thread order will be distinct between these two options (beyond being simply reversed). When sorting by oldest-first the threads will be sorted by the oldest message in each thread, but when sorting by newest-first the threads will be sorted by the newest message in each thread. By default, results will be displayed in reverse chronological order, (that is, the newest results will be displayed first). --offset=[-]N Skip displaying the first N results. With the leading '-', start at the Nth result from the end. --limit=N Limit the number of displayed results to N. --exclude=(true|false|flag) Specify whether to omit messages matching search.tag_exclude from the search results (the default) or not. The extra option flag only has an effect when --output=summary In this case all matching threads are returned but the "match count" is the number of matching non-excluded messages in the thread. SEE ALSO
notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5), notmuch-new(1), notmuch-reply(1), notmuch-restore(1), notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1) Notmuch 0.13.2 2012-06-01 NOTMUCH-SEARCH(1)
All times are GMT -4. The time now is 04:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy