178

There are two files called "a.txt" and "b.txt" both have a list of words. Now I want to check which words are extra in "a.txt" and are not in "b.txt".

I need a efficient algorithm as I need to compare two dictionaries.

Elrond_EGLDer
  • 47,430
  • 25
  • 189
  • 180
Ali Imran
  • 8,249
  • 3
  • 35
  • 46

11 Answers11

366

if you have vim installed,try this:

vimdiff file1 file2

or

vim -d file1 file2

you will find it fantastic.enter image description here

Fengya Li
  • 4,060
  • 1
  • 12
  • 12
77

Sort them and use comm:

comm -23 <(sort a.txt) <(sort b.txt)

comm compares (sorted) input files and by default outputs three columns: lines that are unique to a, lines that are unique to b, and lines that are present in both. By specifying -1, -2 and/or -3 you can suppress the corresponding output. Therefore comm -23 a b lists only the entries that are unique to a. I use the <(...) syntax to sort the files on the fly, if they are already sorted you don't need this.

Anders Johansson
  • 3,706
  • 16
  • 18
  • I have added my own answer using only grep commands, please tell me is it more efficient? – Ali Imran Jan 25 '13 at 07:08
  • 3
    @AliImran, `comm` is more efficient because it does the job in a single run, without storing the entire file in memory. Since you're using dictionaries that are most likely already sorted you don't even need to `sort` them. Using `grep -f file1 file2` on the other hand will load the entire `file1` into memory and compare each line in `file2` with all of those entries, which is much less efficient. It's mostly useful for small, unsorted `-f file1`. – Anders Johansson Jan 26 '13 at 01:56
  • 1
    Thanks @AndersJohansson for sharing the "comm" command. Its nifty indeed. I frequently have to do outer joins between files and this does the trick. – blispr Jul 31 '17 at 15:31
  • Pay attention to the new line character... I just found that `\n` will also be included to do comparing. – Bin Aug 16 '17 at 10:26
34

Try sdiff (man sdiff)

sdiff -s file1 file2
Rustam A. Gasanov
  • 13,604
  • 8
  • 54
  • 72
mudrii
  • 639
  • 6
  • 4
34

If you prefer the diff output style from git diff, you can use it with the --no-index flag to compare files not in a git repository:

git diff --no-index a.txt b.txt

Using a couple of files with around 200k file name strings in each, I benchmarked (with the built-in timecommand) this approach vs some of the other answers here:

git diff --no-index a.txt b.txt
# ~1.2s

comm -23 <(sort a.txt) <(sort b.txt)
# ~0.2s

diff a.txt b.txt
# ~2.6s

sdiff a.txt b.txt
# ~2.7s

vimdiff a.txt b.txt
# ~3.2s

comm seems to be the fastest by far, while git diff --no-index appears to be the fastest approach for diff-style output.


Update 2018-03-25 You can actually omit the --no-index flag unless you are inside a git repository and want to compare untracked files within that repository. From the man pages:

This form is to compare the given two paths on the filesystem. You can omit the --no-index option when running the command in a working tree controlled by Git and at least one of the paths points outside the working tree, or when running the command outside a working tree controlled by Git.

joelostblom
  • 25,984
  • 12
  • 108
  • 120
29

You can use diff tool in linux to compare two files. You can use --changed-group-format and --unchanged-group-format options to filter required data.

Following three options can use to select the relevant group for each option:

  • '%<' get lines from FILE1

  • '%>' get lines from FILE2

  • '' (empty string) for removing lines from both files.

E.g: diff --changed-group-format="%<" --unchanged-group-format="" file1.txt file2.txt

[root@vmoracle11 tmp]# cat file1.txt 
test one
test two
test three
test four
test eight
[root@vmoracle11 tmp]# cat file2.txt 
test one
test three
test nine
[root@vmoracle11 tmp]# diff --changed-group-format='%<' --unchanged-group-format='' file1.txt file2.txt 
test two
test four
test eight
Martijn Courteaux
  • 63,780
  • 43
  • 187
  • 279
Manjula
  • 4,494
  • 3
  • 25
  • 36
9

You can also use: colordiff: Displays the output of diff with colors.

About vimdiff: It allows you to compare files via SSH, for example :

vimdiff /var/log/secure scp://192.168.1.25/var/log/secure

Extracted from: http://www.sysadmit.com/2016/05/linux-diferencias-entre-dos-archivos.html

FindlinuxOne
  • 91
  • 1
  • 1
6

Also, do not forget about mcdiff - Internal diff viewer of GNU Midnight Commander.

For example:

mcdiff file1 file2

Enjoy!

Iurii Golskyi
  • 703
  • 1
  • 12
  • 22
4

Use comm -13 (requires sorted files):

$ cat file1
one
two
three

$ cat file2
one
two
three
four

$ comm -13 <(sort file1) <(sort file2)
four
Chris Seymour
  • 75,961
  • 24
  • 144
  • 187
1

Here is my solution for this :

mkdir temp
mkdir results
cp /usr/share/dict/american-english ~/temp/american-english-dictionary
cp /usr/share/dict/british-english ~/temp/british-english-dictionary
cat ~/temp/american-english-dictionary | wc -l > ~/results/count-american-english-dictionary
cat ~/temp/british-english-dictionary | wc -l > ~/results/count-british-english-dictionary
grep -Fxf ~/temp/american-english-dictionary ~/temp/british-english-dictionary > ~/results/common-english
grep -Fxvf ~/results/common-english ~/temp/american-english-dictionary > ~/results/unique-american-english
grep -Fxvf ~/results/common-english ~/temp/british-english-dictionary > ~/results/unique-british-english
Ali Imran
  • 8,249
  • 3
  • 35
  • 46
  • 2
    Did you try any of the other solutions? Did one of these solutions was useful to you? Your question is generic enough to draw in many users, but your answer is more specific for my taste... For my particular case `sdiff -s file1 file2` was useful. – Metafaniel Apr 21 '15 at 19:50
  • @Metafaniel my solution do not use sdiff command. It only use linux built in commands to solve the problem. – Ali Imran Apr 24 '15 at 15:25
0

You can also use:

sdiff file1 file2

To display differences side by side within your terminal!

otto_
  • 21
  • 2
-1

Using awk for it. Test files:

$ cat a.txt
one
two
three
four
four
$ cat b.txt
three
two
one

The awk:

$ awk '
NR==FNR {                    # process b.txt  or the first file
    seen[$0]                 # hash words to hash seen
    next                     # next word in b.txt
}                            # process a.txt  or all files after the first
!($0 in seen)' b.txt a.txt   # if word is not hashed to seen, output it

Duplicates are outputed:

four
four

To avoid duplicates, add each newly met word in a.txt to seen hash:

$ awk '
NR==FNR {
    seen[$0]
    next
}
!($0 in seen) {              # if word is not hashed to seen
    seen[$0]                 # hash unseen a.txt words to seen to avoid duplicates 
    print                    # and output it
}' b.txt a.txt

Output:

four

If the word lists are comma-separated, like:

$ cat a.txt
four,four,three,three,two,one
five,six
$ cat b.txt
one,two,three

you have to do a couple of extra laps (forloops):

awk -F, '                    # comma-separated input
NR==FNR {
    for(i=1;i<=NF;i++)       # loop all comma-separated fields
        seen[$i]
    next
}
{
    for(i=1;i<=NF;i++)
        if(!($i in seen)) {
             seen[$i]        # this time we buffer output (below):
             buffer=buffer (buffer==""?"":",") $i
        }
    if(buffer!="") {         # output unempty buffers after each record in a.txt
        print buffer
        buffer=""
    }
}' b.txt a.txt

Output this time:

four
five,six
James Brown
  • 31,411
  • 6
  • 31
  • 52