...to specify a file listing .desktop files to exclude from the output.
labwc-menu-generator have this implemented.
+1
This would be so useful for people using window managers.
Heres why. In most configs I see people doing something like this:
meta+e = Thunar
meta+E = ranger
meta+alt+e = PCManFM
meta+alt+E = Dolphin
This can quickly become bothersome, especially if your not using them all the time. As you forget exactly which bind opens your desired application.
Adding a feature like this that allows ignoring OR including a set of entries, means we can use fuzzel to generate bespoke application launchers.
One could argue this can be done in fuzzel's dmenu mode, however this means missing out on the large logo on the bottom of the window present when theres not many entries.
I don't understand. I get why you'd maybe wanna ignore something. Editing a *.desktop file manually IMO isn't a good solution in general. So somekinda blacklist would be good.
For @Sneethe ... i don't get what you mean. Just open fuzzel and search for what you wanna open? All desktop files are included by default... so i'm confused about what exactly you want to achieve.
. Editing a *.desktop file manually IMO isn't a good solution in general. So somekinda blacklist would be good.
The XDG Desktop Entries standard for .desktop files is designed to cover this case, specifying that if you don't want to display a file, you can add a .desktop file to ~/.local/share/applicationswith NoDisplay=true. Then every launcher-- not just Fuzzel-- will respect hiding that app.
Fuzzel should already support "bespoke application launchers" because it supports the XDG_DATA_HOME and XDG_DATA_DIRS environment variables. These could be better documented by Fuzzel.
https://specifications.freedesktop.org/basedir-spec/latest/
In theory, you could launch Fuzzel with these set a different value for a bespoke menu. It would work by symlink any apps you want to appear in this menu into an "applications" sub directory of your custom XDG_DATA_HOME value.
In practice, I tried some and could not get this to work easily. Part of the issue is that XDG_DATA_HOME is also used as a search path for icons, so you have to make sure your private directory sets up the icons as well.
The other workaround already offered is to pre-fill the with the --search option as well to specify which fields are searched with the --fields option.
For example, to bring up a menu that contains only apps related to settings, you could use:
fuzzel --search settings --fields=categories,keywords
Though the problem with that approach is that after the menu is displayed, you can't actually fuzzy match on the name....
So I'm agreeing with the problem statement that Fuzzel could better support creating "bespoke" menus, although I'm not sure adding the --ignore flag is best way to do it.
We should also explore better ways to express what you do want in the menu instead of what you don't.
. Editing a *.desktop file manually IMO isn't a good solution in general. So somekinda blacklist would be good.
The XDG Desktop Entries standard for .desktop files is designed to cover this case, specifying that if you don't want to display a file, you can add a .desktop file to
~/.local/share/applicationswithNoDisplay=true. Then every launcher-- not just Fuzzel-- will respect hiding that app.
I know. It's still a bad solution to manually touch those files. Those files can easily be overwritten on updates and if you overwrite it yourself in your local apps folder, you will need to watch out for changes in the "original" desktop file as well.
What i do in Walker is a simple array of regexps. This allows to also just ignore single actions instead of the whole desktop file. IMO that's a good solution.
It's still a bad solution to manually touch those files.
The purpose of files in ~/.local/share/applications is to be touched by use.
Those files can easily be overwritten on updates
No, package updates don't touch this folder. Packages get updated in /usr/share/applications or in Flatpaks.
If you want to ignore all Desktop actions, Fuzzel has an option to disable those.
I tested this one-liner will disable the display of a .desktop file. You need to find the file name from /usr/local/share/applications first:
echo -e '[Desktop Entry]\nNoDisplay=true'>~/.local/share/applications/electron32.desktop
This covers the global case. I'm leaving this issue open to consider the use for "bespoke" cases like:
"Build me a menu which includes only files in the Settings category but ignores the printing app I have installed".
I'm still not convinced this couldn't be covered with other methods already supported to load .desktop from different directories, though.
i know this is an old thread, but what about filtering by matches in filenames? using something like match-exclude=wine, waydroid, calf would prevent editing those files and keep the config less cluttered. Especially in cases like Waydroid, which generates a lot of unwanted entries.
i made a very quick implementation, it only adds regex.h as extra header), but wanna ask before doing a possible PR
Without filtering (using lastest fuzzel version):
image
Filtering all entries with "a" in their filename:
image
Filtering other specific entries:
image
Passing filtering as argument:
image
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?