Extending Context Menu Functionality

Have a suggestion for "Everything"? Please post it here.
Native2904
Posts: 112
Joined: Mon Nov 22, 2021 8:36 pm

Extending Context Menu Functionality

Post by Native2904 »

Hi Void,

I don’t want to come across as disrespectful..
—especially since I’ve raised a similar question before
and I want to emphasize that I truly love this program.

That said, I’d like to suggest an idea to expand the context menu’s capabilities.

  • The ability to cascade entries
  • The ability to make entries dependent on search patterns
  • The ability to detect whether one or multiple files are selected

2026-04-04_234544.png
You do not have the required permissions to view the files attached to this post.
void
Developer
Posts: 19899
Joined: Fri Oct 16, 2009 11:31 pm

Re: Extending Context Menu Functionality

Post by void »

Thank you for the feedback and suggestions Native2904,


The ability to cascade entries
I will look into support for specifying submenus with \
I already have code to do this with menu_folders, but custom_open_commands doesn't use it.


The ability to make entries dependent on search patterns
I want to rewrite Tools -> Options -> Context Menu and add full customization support here.
This will not happen for Everything 1.5, but maybe in a future version of Everything.
I will consider search patterns. I am not keen on search patterns as searches can be complex.
I would rather have a simple $content-search: function, which could be used in the filter and command.
$content-search: in the filter will only match if there's a content search.
$content-search: in the command would be replaced with the first content search.


The ability to detect whether one or multiple files are selected
I will consider a filter function to match a single selection or multiple selections.
Thank you for the suggestions.
soul4kills
Posts: 39
Joined: Mon Sep 04, 2023 4:12 am

Re: Extending Context Menu Functionality

Post by soul4kills »

void wrote: Sat Apr 04, 2026 11:13 pm Thank you for the feedback and suggestions Native2904,


The ability to cascade entries
I will look into support for specifying submenus with \
I already have code to do this with menu_folders, but custom_open_commands doesn't use it.


The ability to make entries dependent on search patterns
I want to rewrite Tools -> Options -> Context Menu and add full customization support here.
This will not happen for Everything 1.5, but maybe in a future version of Everything.
I will consider search patterns. I am not keen on search patterns as searches can be complex.
I would rather have a simple $content-search: function, which could be used in the filter and command.
$content-search: in the filter will only match if there's a content search.
$content-search: in the command would be replaced with the first content search.


The ability to detect whether one or multiple files are selected
I will consider a filter function to match a single selection or multiple selections.
Thank you for the suggestions.
Any plans to only show custom menu items based on the search context? To minimize menu clutter with a context based approach.

For example. When I use my Music or Media filters, I only want those custom menu items shown when I'm using the specific filter in question. Under any other condition, hide them.

Unless this was covered above and my reading comprehension just sucks. Also, is there an ability to assign a custome menu item the default action when clicking a file?
Last edited by soul4kills on Sat Apr 11, 2026 4:32 pm, edited 1 time in total.
Native2904
Posts: 112
Joined: Mon Nov 22, 2021 8:36 pm

Re: Extending Context Menu Functionality

Post by Native2904 »

But if you put *.flac or *.mp3 in your filter box then the context menu only appears when you click on this extensions...
void
Developer
Posts: 19899
Joined: Fri Oct 16, 2009 11:31 pm

Re: Extending Context Menu Functionality

Post by void »

When I use my Music or Media filters, I only want those custom menu items shown when I'm using the specific filter in question
Use the filter in your Custom Open Commands to limit the custom context menu item to media files only.


Also, is there an ability to assign a custome menu item the default action when clicking a file?
Leave the Name in your Custom Open Commands blank to make it the default action.
soul4kills
Posts: 39
Joined: Mon Sep 04, 2023 4:12 am

Re: Extending Context Menu Functionality

Post by soul4kills »

void wrote: Sat Apr 11, 2026 10:42 pm
When I use my Music or Media filters, I only want those custom menu items shown when I'm using the specific filter in question
Use the filter in your Custom Open Commands to limit the custom context menu item to media files only.


Also, is there an ability to assign a custome menu item the default action when clicking a file?
Leave the Name in your Custom Open Commands blank to make it the default action.
Your solution to set default works.

Your solution to restrict custom menu command usage to just a specific search filter didn't seem to work. Is this what you meant?
image.png
You do not have the required permissions to view the files attached to this post.
void
Developer
Posts: 19899
Joined: Fri Oct 16, 2009 11:31 pm

Re: Extending Context Menu Functionality

Post by void »

The filter cannot reference macros.

Please try the following filter instead:

Code: Select all

ext:aac;ac3;adt;adts;aif;aifc;aiff;amr;ape;au;cda;dts;ec3;fla;flac;lpcm;m1a;m2a;m3u;m3u8;m4a;m4b;m4p;mid;midi;mka;mp2;mp3;mpa;mpc;oga;ogg;opus;ra;rmi;snd;wav;wax;weba;wma;3g2;3gp;3gp2;3gpp;amv;asf;asx;avi;bdmv;bik;d2v;divx;drc;dsa;dsm;dss;dsv;evo;f4v;flc;fli;flic;flv;hdmov;ifo;ivf;m1v;m2p;m2t;m2ts;m2v;m4v;mkv;mod;mov;mp2v;mp4;mp4v;mpe;mpeg;mpg;mpls;mpv2;mpv4;mts;ogm;ogv;ogx;pss;pva;qt;ram;ratdvd;rm;rmm;rmvb;roq;rpm;smil;smk;swf;tod;tp;tpr;ts;tts;uvu;vob;vp6;webm;wm;wmp;wmv;wmx;wvx