-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Apps] All file-types from Desktop get listed #137
Comments
The most obvious change that would blend best to the existing features would be to add a An ideal solution is to roll up an extra package that would allow real file filtering (i.e. wildcards, perhaps regex; with include/exclude rules). In fact this has been (partly) requested already (see #24). I have the features listing and design ready since quite a while but didn't have time to start its development. Bonus is we could leave the |
Oh, I see you are aware of this behaviour and have already plans regarding this! :) So I'll close this issue. |
I'm reopening this until the |
|
Version number
Keypirinha 2.9.9 for x64
Package
Apps
Issue description
With the default configuration (
scan_start_menu
andscan_env_path
enabled) all file-types located at the Desktop get listed and not only executables (or links to executables).I think that this behaviour is not consistent with the one for directories listed in
PATH
orextra_paths
.(Personally, I didn't expect Desktop to get scanned at all ^_^)
Steps for reproducing
Expected behaviour: File should not be listed.
Actual behaviour: File gets listed.
Suggestion for fix/change
I think the inital problem is, that the items located at the start menu are not executable files, but windows-shortcuts. Nevertheless, we know that all these will link to executables so we can ignore
scan_env_path
in_catalog_startmenu
.But Desktop can contain different file-types. Therefore in this special case we should look for executables and for shortcuts, but only which one are linking to executables!
(Another way could be just not to look inside Desktop)
The text was updated successfully, but these errors were encountered: