It seems the difference has to do with the Content-Length header and how it is treated by both commands. But before going into that, curl -X HEAD does not give any output because, by default, curl does not print headers if switch -i is not provided (not needed on -I though). In any case, curl … Read more
Try comm Another way to look at it: Show lines that only exist in file a: (i.e. what was deleted from a) comm -23 a b Show lines that only exist in file b: (i.e. what was added to b) comm -13 a b Show lines that only exist in one file or the other: … Read more
You can do it with Bash’s process substitution: diff foo <(ssh myServer ‘cat foo’) Or, if both are on remote servers: diff <(ssh myServer1 ‘cat foo’) <(ssh myServer2 ‘cat foo’)
You can use ndiff in the difflib module to do this. It has all the information necessary to convert one string into another string. A simple example: prints:
It should just be: –cached means show the changes in the cache/index (i.e. staged changes) against the current HEAD. –staged is a synonym for –cached. –staged and –cached does not point to HEAD, just difference with respect to HEAD. If you cherry pick what to commit using git add –patch (or git add -p), –staged will return what is staged.
GitHub suggests that you should make sure to only use \n as a newline character in git-handled repos. There’s an option to auto-convert: Of course, this is said to convert crlf to lf, while you want to convert cr to lf. I hope this still works … And then convert your files: core.autocrlf is described on the … Read more
You can actually compare files natively right in Sublime Text. Navigate to the folder containing them through Open Folder… or in a project Select the two files (ie, by holding Ctrl on Windows or ⌘ on macOS) you want to compare in the sidebar Right click and select the Diff files… option.
diff has some options that can be useful to you: So diff -w old new should ignore all spaces and thus report only substantially different lines.
To see the diff for a particular COMMIT hash, where COMMIT is the hash of the commit: git diff COMMIT~ COMMIT will show you the difference between that COMMIT‘s ancestor and the COMMIT. See the man pages for git diff for details about the command and gitrevisions about the ~ notation and its friends. Alternatively, … Read more
Run this in the CMD shell or batch file: FC can also be used to compare binary files: