Suppress GFileInfo related warnings#119
Open
mtasaka wants to merge 3 commits into
Open
Conversation
https://gitlab.gnome.org/GNOME/glib/-/issues/3068 says that when GFileInfo is created via g_file_enumerate_children then g_file_enumerator_next_file , calling g_file_info_has_attribute beforehand is always needed for standard::is-hidden or standard::content-type (or so), even if GFileQueryInfoFlags is correctly specified. Closes lxde#118 .
Contributor
Author
|
2dd896c is additional fix for this issue, which is found when showing the result of search dialog. I think this PR is better to merge and I would appreciate it if this PR is reviewed, thank you. |
…indow More fix for lxde#118 .
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://gitlab.gnome.org/GNOME/glib/-/issues/3068 says that when GFileInfo is created via g_file_enumerate_children then g_file_enumerator_next_file , calling g_file_info_has_attribute beforehand is always needed for standard::is-hidden or standard::content-type (or so), even if GFileQueryInfoFlags is correctly specified.
Closes #118 .