123

I want to run ack or grep on HTML files that often have very long lines. I don't want to see very long lines that wrap repeatedly. But I do want to see just that portion of a long line that surrounds a string that matches the regular expression. How can I get this using any combination of Unix tools?

Benjamin W.
  • 46,058
  • 19
  • 106
  • 116
dan
  • 43,914
  • 47
  • 153
  • 254
  • 2
    What's `ack`? Is it a command you use when you don't like something? Something like `ack file_with_long_lines | grep pattern`? :-) – Alok Singhal Jan 09 '10 at 20:27
  • 8
    @Alok `ack` (known as `ack-grep` on Debian) is `grep` on steroids. It also has the `--thpppt` option (not kidding). http://betterthangrep.com/ – ZoogieZork Jan 09 '10 at 20:33
  • Thanks. I learned something today. – Alok Singhal Jan 09 '10 at 20:37
  • 1
    While the `--thpppt` feature is somewhat controversial, the key advantage appears to be that you can use Perl regexes directly, not some crazy `[[:space:]]` and characters like `{`, `[`, etc. changing meaning with the `-e` and `-E` switches in a way that's impossible to remember. – Evgeni Sergeev Jan 03 '14 at 07:03
  • Similar: https://unix.stackexchange.com/q/163726 and https://stackoverflow.com/q/8101701 – sondra.kinsey Sep 15 '19 at 17:27
  • I use `grep --color=always | less -S -R`. Then, type `-R` to unfold/fold the lines. – Jérôme Pouiller Aug 11 '20 at 07:39

10 Answers10

122

You could use the grep options -oE, possibly in combination with changing your pattern to ".{0,10}<original pattern>.{0,10}" in order to see some context around it:

       -o, --only-matching
              Show only the part of a matching line that matches PATTERN.

       -E, --extended-regexp
             Interpret pattern as an extended regular expression (i.e., force grep to behave as egrep).

For example (from @Renaud's comment):

grep -oE ".{0,10}mysearchstring.{0,10}" myfile.txt

Alternatively, you could try -c:

       -c, --count
              Suppress normal output; instead print a count of matching  lines
              for  each  input  file.  With the -v, --invert-match option (see
              below), count non-matching lines.
Paul
  • 3,920
  • 31
  • 29
Ether
  • 53,118
  • 13
  • 86
  • 159
  • 52
    an example: grep -oE ".{0,20}mysearchstring.{0,20}" myfile – Renaud Nov 09 '12 at 10:10
  • 17
    you should change the answer to add -E option as shown by @Renaud (extended pattern option), or the proposed pattern for extending context wont work. – kriss Oct 28 '13 at 13:30
  • 1
    Not that necessary maybe but here's an example: `$ echo "eeeeeeeeeeeeeeeeeeeeqqqqqqqqqqqqqqqqqqqqMYSTRINGwwwwwwwwwwwwwwwwwwwwrrrrrrrrrrrrrrrrrrrrr" > fileonelongline.txt && grep -oE ".{0,20}MYSTRING.{0,20}" ./fileonelongline.txt ` prints `qqqqqqqqqqqqqqqqqqqqMYSTRINGwwwwwwwwwwwwwwwwwwww` – Ulises Layera Nov 21 '18 at 17:30
  • 1
    This works well; but notable downside is that when using, e.g., `oE ".{0,20}mysearchstring.{0,20}"`, you lose the highlighting of the inner "original" string against the context, because the whole thing becomes the search pattern. Would love to find a way to keep some non-highlighted context around the search results, for much easier visual scanning and result interpretation. – Aaron Wallentine Sep 18 '20 at 05:55
  • 3
    Oh, here's a solution to the highlighting problem caused by using the `-oE ".{0,x}foo.{0,x}"` approach (where `x` is the number of characters of context) -- append ` | grep foo ` to the end. Works for either ack or grep solutions. More solutions also here: https://unix.stackexchange.com/questions/163726/limit-grep-context-to-n-characters-on-line – Aaron Wallentine Sep 18 '20 at 06:11
55

Pipe your results thru cut. I'm also considering adding a --cut switch so you could say --cut=80 and only get 80 columns.

Ronan Boiteau
  • 9,608
  • 6
  • 34
  • 56
Andy Lester
  • 91,102
  • 13
  • 100
  • 152
28

You could use less as a pager for ack and chop long lines: ack --pager="less -S" This retains the long line but leaves it on one line instead of wrapping. To see more of the line, scroll left/right in less with the arrow keys.

I have the following alias setup for ack to do this:

alias ick='ack -i --pager="less -R -S"' 
Jonah Braun
  • 4,155
  • 7
  • 29
  • 31
15

grep -oE ".{0,10}error.{0,10}" mylogfile.txt

In the unusual situation where you cannot use -E, use lowercase -e instead.

Explanation: illustrative command explanation

Socob
  • 1,189
  • 1
  • 12
  • 26
Josh Withee
  • 9,922
  • 3
  • 44
  • 62
14

To get characters from 1 to 100.

cut -c 1-100

You might want to base the range off the current terminal, e.g.

cut -c 1-$(tput cols)
ideasman42
  • 42,413
  • 44
  • 197
  • 320
edib
  • 812
  • 1
  • 11
  • 20
2

Taken from: http://www.topbug.net/blog/2016/08/18/truncate-long-matching-lines-of-grep-a-solution-that-preserves-color/

The suggested approach ".{0,10}<original pattern>.{0,10}" is perfectly good except for that the highlighting color is often messed up. I've created a script with a similar output but the color is also preserved:

#!/bin/bash

# Usage:
#   grepl PATTERN [FILE]

# how many characters around the searching keyword should be shown?
context_length=10

# What is the length of the control character for the color before and after the
# matching string?
# This is mostly determined by the environmental variable GREP_COLORS.
control_length_before=$(($(echo a | grep --color=always a | cut -d a -f '1' | wc -c)-1))
control_length_after=$(($(echo a | grep --color=always a | cut -d a -f '2' | wc -c)-1))

grep -E --color=always "$1" $2 |
grep --color=none -oE \
    ".{0,$(($control_length_before + $context_length))}$1.{0,$(($control_length_after + $context_length))}"

Assuming the script is saved as grepl, then grepl pattern file_with_long_lines should display the matching lines but with only 10 characters around the matching string.

Benjamin W.
  • 46,058
  • 19
  • 106
  • 116
xuhdev
  • 8,018
  • 2
  • 41
  • 69
  • Works, but outputs trailing junk for me, like this: ^\[\[?62;9;c. I haven't tried debugging because [@Jonah Braun's answer](https://stackoverflow.com/a/11038776) satisfied me. – sondra.kinsey Sep 15 '18 at 21:18
2

I put the following into my .bashrc:

grepl() {
    $(which grep) --color=always $@ | less -RS
}

You can then use grepl on the command line with any arguments that are available for grep. Use the arrow keys to see the tail of longer lines. Use q to quit.

Explanation:

  • grepl() {: Define a new function that will be available in every (new) bash console.
  • $(which grep): Get the full path of grep. (Ubuntu defines an alias for grep that is equivalent to grep --color=auto. We don't want that alias but the original grep.)
  • --color=always: Colorize the output. (--color=auto from the alias won't work since grep detects that the output is put into a pipe and won't color it then.)
  • $@: Put all arguments given to the grepl function here.
  • less: Display the lines using less
  • -R: Show colors
  • S: Don't break long lines
pt1
  • 179
  • 1
  • 5
2

The Silver Searcher (ag) supports its natively via the --width NUM option. It will replace the rest of longer lines by [...].

Example (truncate after 120 characters):

 $ ag --width 120 '@patternfly'
 ...
 1:{"version":3,"file":"react-icons.js","sources":["../../node_modules/@patternfly/ [...]

In ack3, a similar feature is planned but currently not implemented.

Philipp Claßen
  • 41,306
  • 31
  • 146
  • 239
  • but in `ag`, the width "begins" with first character, so this doesn't quite work when the string is in the middle of a very long line – Paul Feb 10 '23 at 01:17
1

Here's what I do:

function grep () {
  tput rmam;
  command grep "$@";
  tput smam;
}

In my .bash_profile, I override grep so that it automatically runs tput rmam before and tput smam after, which disabled wrapping and then re-enables it.

ognockocaten
  • 814
  • 9
  • 18
0

ag can also take the regex trick, if you prefer it:

ag --column -o ".{0,20}error.{0,20}"
Luke Miles
  • 941
  • 9
  • 19