How can you see if a file is lfs now?
That is my primary use case, to see that a binary file is properly added.

Save as may be useful for some, sure.

Diff and view is not interesting for me, these files are binary or very large normally, it is just to get something that seem complete.

How can you see if a file is lfs now? That is my primary use case, to see that a binary file is properly added.

What is missing for you?

LFS file added:

a.bin is a file which is not detected as binary by GE's heuristic.

0.bin contains a zero byte. I admit, there is no clear indication that the file "differs" because of being turned into an LFS pointer. At least, one can see that the file is affected.
But this affects only the commit where files are moved to LFS belatedly - (which should be avoided anyway).

LFS file changed:

(looks the same regardless of the heuristic for binary files)

Large text files

a.long is handled differently on purpose. It has been configured to be diffed as text by defining an adapted diff filter:

git config diff.lfs-text.textconv cat

*.long filter=lfs diff=lfs-text merge=lfs -text

New LFS file

looks the same for "Index" and real commit

If really in doubt, there is a mix of related LFS commands:

git lfs ls-files --all
git lfs status
git lfs fsck
git add --renormalize *

Save as may be useful for some, sure.

It was useless and rather a bug because of its unexpected behavior. (It transparently works for difftool. Why not for "Save as" and for displaying the picture of the second revision?)

A missing separate feature is to provide a context menu item for git lfs track <file.ext>.
I think of a TaskDialog asking whether to track that file or all files with its extension, i.e. "*.ext".

A missing separate feature is to provide a context menu item for git lfs track <file.ext>. I think of a TaskDialog asking whether to track that file or all files with its extension, i.e. "*.ext".

Also: #8355 & #8344 (lock/unlock LFS feature)

What is missing for you?

To see if a file is handled by lfs or not. This can be done in other ways, maybe in the context menu.
In your example repo, it is just GitExtensionsLogoWide.png where the behaviour is changed, the other are still displayed as lfs.
(I expected a.long too from the diff tab too as attributes were changed.)

and my opinions is probably the important here, this is plugging something that users see as a problem (but it is not really that).
A way to display this can be added later.

I expected a.long too from the diff tab too as attributes were changed.

You need to run configure_lfs-text.sh, i.e git config diff.lfs-text.textconv cat.

To see if a file is handled by lfs or not. This can be done in other ways, maybe in the context menu.
In your example repo, it is just GitExtensionsLogoWide.png where the behaviour is changed, the other are still displayed as lfs.

This PR is about getting / saving selected files. Refer to the issue being fixed, please!
Whether a file is tracked by LFS or not and changing this state, is a separate feature.
I am changing the PR title.

I am not thrilled to not see if the image file is handled or not, but approving.