[request] CHGrep

sud_crow · 2006-04-03 04:56:10

Hi, anyone has a pkgbuild for chgrep?
Its a real usefull app that allows to replace strings in files using something similar to grep, but easier.

Just in case:
http://freshmeat.net/projects/chgrep/

tomk · 2006-04-03 09:21:54

Easier than grep? What could be easier than grep?

Usage: grep [OPTION]... PATTERN [FILE] ...
Search for PATTERN in each FILE or standard input.
Example: grep -i 'hello world' menu.h main.c

Regexp selection and interpretation:
  -E, --extended-regexp     PATTERN is an extended regular expression
  -F, --fixed-strings       PATTERN is a set of newline-separated strings
  -G, --basic-regexp        PATTERN is a basic regular expression
  -P, --perl-regexp         PATTERN is a Perl regular expression
  -e, --regexp=PATTERN      use PATTERN as a regular expression
  -f, --file=FILE           obtain PATTERN from FILE
  -i, --ignore-case         ignore case distinctions
  -w, --word-regexp         force PATTERN to match only whole words
  -x, --line-regexp         force PATTERN to match only whole lines
  -z, --null-data           a data line ends in 0 byte, not newline

Miscellaneous:
  -s, --no-messages         suppress error messages
  -v, --invert-match        select non-matching lines
  -V, --version             print version information and exit
      --help                display this help and exit
      --mmap                use memory-mapped input if possible

Output control:
  -m, --max-count=NUM       stop after NUM matches
  -b, --byte-offset         print the byte offset with output lines
  -n, --line-number         print line number with output lines
      --line-buffered       flush output on every line
  -H, --with-filename       print the filename for each match
  -h, --no-filename         suppress the prefixing filename on output
      --label=LABEL         print LABEL as filename for standard input
  -o, --only-matching       show only the part of a line matching PATTERN
  -q, --quiet, --silent     suppress all normal output
      --binary-files=TYPE   assume that binary files are TYPE
                            TYPE is 'binary', 'text', or 'without-match'
  -a, --text                equivalent to --binary-files=text
  -I                        equivalent to --binary-files=without-match
  -d, --directories=ACTION  how to handle directories
                            ACTION is 'read', 'recurse', or 'skip'
  -D, --devices=ACTION      how to handle devices, FIFOs and sockets
                            ACTION is 'read' or 'skip'
  -R, -r, --recursive       equivalent to --directories=recurse
      --include=PATTERN     files that match PATTERN will be examined
      --exclude=PATTERN     files that match PATTERN will be skipped.
      --exclude-from=FILE   files that match PATTERN in FILE will be skipped.
  -L, --files-without-match only print FILE names containing no match
  -l, --files-with-matches  only print FILE names containing matches
  -c, --count               only print a count of matching lines per FILE
  -Z, --null                print 0 byte after FILE name

Context control:
  -B, --before-context=NUM  print NUM lines of leading context
  -A, --after-context=NUM   print NUM lines of trailing context
  -C, --context=NUM         print NUM lines of output context
  -NUM                      same as --context=NUM
      --color[=WHEN],
      --colour[=WHEN]       use markers to distinguish the matching string
                            WHEN may be `always', `never' or `auto'.
  -U, --binary              do not strip CR characters at EOL (MSDOS)
  -u, --unix-byte-offsets   report offsets as if CRs were not there (MSDOS)

`egrep' means `grep -E'.  `fgrep' means `grep -F'.
With no FILE, or when FILE is -, read standard input.  If less than
two FILEs given, assume -h.  Exit status is 0 if match, 1 if no match,
and 2 if trouble.

Seriously - chgrep is now in the AUR here - enjoy.

sud_crow · 2006-04-05 03:05:13

Thanks Tom

I was making my own, but i alway miss something, although they usually work (and it did), im sure i have something wrong, as in this case, this line:

#find $startdir/pkg -name '*.la' -exec rm {} ;

whats that?
Thanks!

tomk · 2006-04-05 08:57:16

Damn. :oops: I should have deleted that.

That line is commented, sud_crow, so it doesn't actually do anything. If you uncomment it, it's the libtool-slay command, so I keep it in my PKGBUILD.proto in case it's needed.

There's nothing to miss with chgrep - it's a completely standard configure/make/make install, as you've already discovered. In fact, if you'd like to take it over in the AUR, let me know - I'd be happy to orphan it for you.

sud_crow · 2006-04-06 00:20:11

Ooops, i didnt realize the #... i was thinking in the ]#... lol, that's a consequence of seeing so much code on forums and so little in practice

If you would like to free yourself of it, i would accept it with no problem...

Thanks again.

tomk · 2006-04-07 22:05:18

Ok, it's all yours. I've left a comment to say that you will be adopting it.

Time to get stuck in......:D

sud_crow · 2006-04-08 00:46:40

Ok, thanks!

Mmmm.... :oops: how do i 'adopt' it?

T-Dawg · 2006-04-08 01:23:31

sud_crow wrote:

Ok, thanks!

Mmmm.... :oops: how do i 'adopt' it?

Try pressing the button 'adopt' button

sud_crow · 2006-04-21 06:12:57

I didnt reply before because i was still trying to solve the network issue (and Im still working on it).

I didnt see any adopt button because i didnt had an account on the AUR, i forget sometimes that i have to login to every and each of the services on the site. Its done now though.
I already adopted it, and if all goes well, plan to adopt a few im interested in keeping up to date too.

Regards

_Gandalf_ · 2006-04-21 08:23:53

P.S: you can use <code>options=('NOLIBTOOL')</code> instead of hardcoding the libtool slay

tomk · 2006-04-21 08:39:04

That's cool, Gandalf - where did you find it? It's not in man makepkg, with the other options.

_Gandalf_ · 2006-04-21 08:45:39

in the code of makepkg...

Arch Linux

#1 2006-04-03 04:56:10

[request] CHGrep

#2 2006-04-03 09:21:54

Re: [request] CHGrep

#3 2006-04-05 03:05:13

Re: [request] CHGrep

#4 2006-04-05 08:57:16

Re: [request] CHGrep

#5 2006-04-06 00:20:11

Re: [request] CHGrep

#6 2006-04-07 22:05:18

Re: [request] CHGrep

#7 2006-04-08 00:46:40

Re: [request] CHGrep

#8 2006-04-08 01:23:31

Re: [request] CHGrep

#9 2006-04-21 06:12:57

Re: [request] CHGrep

#10 2006-04-21 08:23:53

Re: [request] CHGrep

#11 2006-04-21 08:39:04

Re: [request] CHGrep

#12 2006-04-21 08:45:39

Re: [request] CHGrep

Board footer