PrestoSoft Community

Another option is to keep the Skip functionality as is and simply exclude resolved diffs from navigation.
A checkbox or button for enabling/disabling this behaviour, plus a default setting, should suffice.

And speaking of skipped blocks, I have a couple of comments:
1. The diff-bar colour of a ...

The problem is that navigating to next/prev difference also considers resolved differences, which makes navigating to *actual* differences inconvenient.

See recording:
https://i.imgur.com/M3skUW4.mp4

Steps to reproduce:
1. Compare 2 files.
2. Using CTRL-F2 set a bookmark in one of the files.
3. Navigate away from the bookmark.
4. Press F5 to re-compare the files
5. Press F2
Expected result: cursor moves to the bookmarked line
Actual result: nothing happens

But wait, there's more!
6. Set ...

Thank you!

Doesn't work when drilling down into individual files.
EDP starts a new instance and does not pass the --no_registry_writing flag

I would appreciate a command-line option not to change the default session for the next launch.
Changing the session almost every time I do a GUI comparison is inconvenient.

I would even go as far as to argue that a session specified on the command line (as opposed to picked in the GUI) is used to ...

Oh, I remember what was the issue.

I intend the "git" session to only be used with git diff, git difftool, etc.

However, after running those commands, EDP remembers the session used and uses it the next time I run EDP.

There should be a way to tell EDP that I am using this session TEMPORARILY, so ...

I just rechecked. You are right, it doesn't update the registry with the folders, just the files (after drilling down).

I would assume so. If I launch EDP with "no history", I expect it to save no history, just like it says on the tin.

That said, I believe that it also saved the folder history, despite being told not to.
I'll check tomorrow.

psguru wrote: Wed Feb 16, 2022 8:47 am

Will /se:Session work in this situation?

Yes, it will.

I tried it. Currently git invokes EDP with these flags: -se:git -nh
However, after I dig into individual files, the history for the file comparison is still saved for the "git" session.

While not ideal, it seems to me that introducing a delay between git calling EDP and the comparison starting might help, especially if there was any way to tell when Defender has stopped examining the newly-copied files. So, have git call (say) a batch file that waits for something (maybe just a ...

I suspect that in this case, FILE_NOTIFY_CHANGE_ATTRIBUTES causes the false positive.
First of of, you can't know without testing your hypothesis.
Which is why I said "I suspect". It could be a different flag.


Second, why is watching for FILE_NOTIFY_CHANGE_ATTRIBUTES is incorrect?
I did not ...

There must be some files that are being created/deleted/modified while the directory comparison view is on. You should be able to inspect your file system to see what they are.
Well, yes and no.

I used the SysInternals Process Monitor to see what processes access the files, trimmed the log to ...

I also asked the same question on SO and got the following comment:
The --dir-diff option pushes all the work off to the diff tool itself: Git just extracts the two commits to be compared into two temporary directories, and then sends the names of the two directories to the diff tool. So everything ...

What exactly do you want to be investigated? I'm not sure what the problem is.

As I wrote above:


Running the following
git difftool --dir-diff <some branch> <some other branch>
Displays a directory comparison as expected, but then I start getting incessant pop-ups that files got changed ...