diff showing only differences inside line












8















I want to compare lines in two files, but to minimize noise in the output, I want only the actual differences in the lines to be printed.



For instance, given the two files below:



a.txt



a b c d e f g h i j k l m n o p q r s t u v w x y z


b.txt



a B c d e f g h i j k l m n o p q r s t u v w x y z


(the difference between them is the case of letter b)



I want the output to be something like:



[-b-]{+B+}


Currently, the best approach I found was to use git diff --word-diff, but it outputs the whole line:



a [-b-]{+B+} c d e f g h i j k l m n o p q r s t u v w x y z


Is there a more direct way to do it, other than manually parsing the output? Also, ideally I would prefer to use something more commonly available than git diff, e.g. a POSIX shell tool that would not require the user to install extra packages.






shell-script diff







share|improve this question

























  • It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

    – Barmar
    14 hours ago











  • Sorry, I added a note describing the difference between the lines.

    – anol
    14 hours ago











  • Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

    – Barmar
    13 hours ago






  • 1





    I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

    – anol
    13 hours ago


















8















I want to compare lines in two files, but to minimize noise in the output, I want only the actual differences in the lines to be printed.



For instance, given the two files below:



a.txt



a b c d e f g h i j k l m n o p q r s t u v w x y z


b.txt



a B c d e f g h i j k l m n o p q r s t u v w x y z


(the difference between them is the case of letter b)



I want the output to be something like:



[-b-]{+B+}


Currently, the best approach I found was to use git diff --word-diff, but it outputs the whole line:



a [-b-]{+B+} c d e f g h i j k l m n o p q r s t u v w x y z


Is there a more direct way to do it, other than manually parsing the output? Also, ideally I would prefer to use something more commonly available than git diff, e.g. a POSIX shell tool that would not require the user to install extra packages.






shell-script diff







share|improve this question

























  • It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

    – Barmar
    14 hours ago











  • Sorry, I added a note describing the difference between the lines.

    – anol
    14 hours ago











  • Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

    – Barmar
    13 hours ago






  • 1





    I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

    – anol
    13 hours ago
















8












8








8


2






I want to compare lines in two files, but to minimize noise in the output, I want only the actual differences in the lines to be printed.



For instance, given the two files below:



a.txt



a b c d e f g h i j k l m n o p q r s t u v w x y z


b.txt



a B c d e f g h i j k l m n o p q r s t u v w x y z


(the difference between them is the case of letter b)



I want the output to be something like:



[-b-]{+B+}


Currently, the best approach I found was to use git diff --word-diff, but it outputs the whole line:



a [-b-]{+B+} c d e f g h i j k l m n o p q r s t u v w x y z


Is there a more direct way to do it, other than manually parsing the output? Also, ideally I would prefer to use something more commonly available than git diff, e.g. a POSIX shell tool that would not require the user to install extra packages.






shell-script diff







share|improve this question
















I want to compare lines in two files, but to minimize noise in the output, I want only the actual differences in the lines to be printed.



For instance, given the two files below:



a.txt



a b c d e f g h i j k l m n o p q r s t u v w x y z


b.txt



a B c d e f g h i j k l m n o p q r s t u v w x y z


(the difference between them is the case of letter b)



I want the output to be something like:



[-b-]{+B+}


Currently, the best approach I found was to use git diff --word-diff, but it outputs the whole line:



a [-b-]{+B+} c d e f g h i j k l m n o p q r s t u v w x y z


Is there a more direct way to do it, other than manually parsing the output? Also, ideally I would prefer to use something more commonly available than git diff, e.g. a POSIX shell tool that would not require the user to install extra packages.






shell-script diff




shell-script diff






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 13 hours ago







anol

















asked 23 hours ago









anolanol

381411




381411













  • It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

    – Barmar
    14 hours ago











  • Sorry, I added a note describing the difference between the lines.

    – anol
    14 hours ago











  • Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

    – Barmar
    13 hours ago






  • 1





    I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

    – anol
    13 hours ago





















  • It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

    – Barmar
    14 hours ago











  • Sorry, I added a note describing the difference between the lines.

    – anol
    14 hours ago











  • Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

    – Barmar
    13 hours ago






  • 1





    I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

    – anol
    13 hours ago



















It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

– Barmar
14 hours ago





It would be nice if you used an example where the differences were more visible. I had to squint to see that those two characters are not the same.

– Barmar
14 hours ago













Sorry, I added a note describing the difference between the lines.

– anol
14 hours ago





Sorry, I added a note describing the difference between the lines.

– anol
14 hours ago













Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

– Barmar
13 hours ago





Why not just use b and B so it's obvious? I understand that this was probably the actual difference, but for purposes of the question you can make it easier.

– Barmar
13 hours ago




1




1





I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

– anol
13 hours ago







I wanted to avoid solutions that would only work on ASCII characters, but since the proposed solution does not depend on it, I changed it. However, I cannot update the answer to reflect the new changes since the edit would be smaller than 6 characters long.

– anol
13 hours ago












1 Answer
1






active

oldest

votes


















14














Using wdiff:



$ wdiff -3 a.txt b.txt



======================================================================

 [-b-] {+B+}

======================================================================


The -3 or ---no-common option will remove words that are common between the two files and only show the differences.



The ===... banner (and empty lines) may be removed with grep:



$ wdiff -3 a.txt b.txt | grep -vx '=*'

 [-b-] {+B+}


wdiff may also read unified diff data if you give it the -d or --diff-input option, for example from git:



git diff somefile | wdiff -d -3


Although wdiff is not a POSIX tool, it is commonly available.






share|improve this answer


























  • It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

    – scohe001
    14 hours ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495228%2fdiff-showing-only-differences-inside-line%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









14














Using wdiff:



$ wdiff -3 a.txt b.txt



======================================================================

 [-b-] {+B+}

======================================================================


The -3 or ---no-common option will remove words that are common between the two files and only show the differences.



The ===... banner (and empty lines) may be removed with grep:



$ wdiff -3 a.txt b.txt | grep -vx '=*'

 [-b-] {+B+}


wdiff may also read unified diff data if you give it the -d or --diff-input option, for example from git:



git diff somefile | wdiff -d -3


Although wdiff is not a POSIX tool, it is commonly available.






share|improve this answer


























  • It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

    – scohe001
    14 hours ago
















14














Using wdiff:



$ wdiff -3 a.txt b.txt



======================================================================

 [-b-] {+B+}

======================================================================


The -3 or ---no-common option will remove words that are common between the two files and only show the differences.



The ===... banner (and empty lines) may be removed with grep:



$ wdiff -3 a.txt b.txt | grep -vx '=*'

 [-b-] {+B+}


wdiff may also read unified diff data if you give it the -d or --diff-input option, for example from git:



git diff somefile | wdiff -d -3


Although wdiff is not a POSIX tool, it is commonly available.






share|improve this answer


























  • It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

    – scohe001
    14 hours ago














14












14








14







Using wdiff:



$ wdiff -3 a.txt b.txt



======================================================================

 [-b-] {+B+}

======================================================================


The -3 or ---no-common option will remove words that are common between the two files and only show the differences.



The ===... banner (and empty lines) may be removed with grep:



$ wdiff -3 a.txt b.txt | grep -vx '=*'

 [-b-] {+B+}


wdiff may also read unified diff data if you give it the -d or --diff-input option, for example from git:



git diff somefile | wdiff -d -3


Although wdiff is not a POSIX tool, it is commonly available.






share|improve this answer















Using wdiff:



$ wdiff -3 a.txt b.txt



======================================================================

 [-b-] {+B+}

======================================================================


The -3 or ---no-common option will remove words that are common between the two files and only show the differences.



The ===... banner (and empty lines) may be removed with grep:



$ wdiff -3 a.txt b.txt | grep -vx '=*'

 [-b-] {+B+}


wdiff may also read unified diff data if you give it the -d or --diff-input option, for example from git:



git diff somefile | wdiff -d -3


Although wdiff is not a POSIX tool, it is commonly available.







share|improve this answer














share|improve this answer



share|improve this answer








edited 13 hours ago

























answered 23 hours ago









KusalanandaKusalananda

124k16236388




124k16236388













  • It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

    – scohe001
    14 hours ago



















  • It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

    – scohe001
    14 hours ago

















It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

– scohe001
14 hours ago





It might be worth noting that if your terminal supports ANSI escapes, you can make wdiff print fancy colored output that's (imo) easier to read with this in your bashrc: alias wdiff="wdiff -n -w $'33[30;41m' -x $'33[0m' -y $'33[30;42m' -z $'33[0m'" (taken from here).

– scohe001
14 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495228%2fdiff-showing-only-differences-inside-line%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Homophylophilia

Image
Haec pagina ad tempus protecta est ob maleficia perpetua. Quaesemus, emendationes suggere in pagina disputationis vel magistratum ad hanc deprotegendam pete. Homophylophilia Hyacinthus complexus ab amante suo Apolline, in pictura Mors Hyacinthi quam Jean Broc pinxit. Homophylophilia est sui sexus vel generis amor vel mores romantici vel sexuales, res venerea masculina in masculos, aut mulier in mulieres appetentes. Hoc ingenium sexuale est "exemplar permanens vel inclinatio ad experiendam sexualem, adfectionalem, vel romanticam vim attrahendi," praecipue vel solum ex hominibus eiusdem sexús; notio "etiam ad hominis iudicium identitatis privatae socialisque in illis attractionibus conditum refert, in moribus quoque qui illos exprimant, et in societate communitatis aliorum qui illos communicent." [1] [2] Per aevos alii aliter rem definiverunt, sed Occidentali nostrae aetatis cultu civili non tantum ad ipsa acta erotica spectat, sed etiam igitur
Read more

Updating UILabel text programmatically using a function

Image
0 so I am trying to update the UIlabel text using a func. I have seen few other questions like mine and I tried their method but it doesn't work. fun returns no value when used in the UIlabel. I have shown my code below.It has to be noted that when I use the function in viewdidload I can retrieve the data. lazy var name: UILabel = { let lb = UILabel() lb.text? = getthename() lb.lineBreakMode = NSLineBreakMode.byWordWrapping lb.textColor = .mainGreen lb.textAlignment = .left lb.font = UIFont.boldSystemFont(ofSize:12.0) return lb }() func getthename() -> String { var wins : String = "" let ud = (Auth.auth().currentUser?.uid) self.ref = Database.database().reference() self.ref.child("Users").child(ud!).observeSingleEvent(of: .value, with: {(snapshot) in
Read more

Cloud Functions - OpenCV Videocapture Read method fails for larger files from cloud storage

Image
0 I created a cloud function to read a video file from cloud storage and read frames and create an image for each frame. This function works for small files which is 1-2 MB, However, this method fails while reading larger file 130 MB. import cv2 from google.cloud import storage vidcap = cv2.VideoCapture("https://storage.googleapis.com/[bucker_name]/[filename.mp4]") if vidcap.isOpened(): vidcap.open("https://storage.googleapis.com/[bucker_name]/[filename.mp4]") success,image = vidcap.read() print(success) Expected the print will return true and an image will hold an image of a first frame. python-3.x function opencv cloud share | improve this question
Read more