Inconsistent behaviors in custom open commands and context menu

Discussion related to "Everything" 1.5.
Post Reply
bigheadghost
Posts: 6
Joined: Tue Aug 15, 2017 2:31 am

Inconsistent behaviors in custom open commands and context menu

Post by bigheadghost »

tested on 1.5.0.1409a x64

Code: Select all

name: ""
filter: ""
command: foo.exe "%1"
foo.exe can accept more than one filenames as arguments

(1) single file (1.txt) selected:
pressing enter will execute the command.
the default item (displayed in bold font) in the context menu is "open", clicking it will do as pressing enter.
All behaviors are as expected.

here comes the wired thing...

(2) single file (1.abc) selected:
pressing enter will execute the command.
the default item in the context menu is "open with" of operating system, clicking it will do as the system, find app in microsoft store...

(3)multiple files selected (1.txt, 2.txt):
pressing enter will open all these selected files with notepad(windows default editor of txt file), not foo.exe designated in the command above.
the default item in the context menu is "open", clicking it do as pressing enter.

(4) multiple files selected (1.abc, 2.abc):
pressing enter will not execute the command, seems nothing happened.
the default item in the context menu is "open", clicking it will do as pressing enter.

(5) change command to: foo.exe "%*", same result. and have one more bug:
it will not double quote filename automatically, regardless of whether %* or "%*" is used.
void
Developer
Posts: 19773
Joined: Fri Oct 16, 2009 11:31 pm

Re: Inconsistent behaviors in custom open commands and context menu

Post by void »

Thank you for the issue reports bigheadghost,

I can confirm the issues.
The issue applies to all versions of Everything 1.5.
I am working on a fix..
void
Developer
Posts: 19773
Joined: Fri Oct 16, 2009 11:31 pm

Re: Inconsistent behaviors in custom open commands and context menu

Post by void »

Everything 1.5 is now beta.

Everything 1.5.0.1410b improves %* in custom open commands.

Everything will now execute all items with the correct command.

Please note that Everything will use the custom open command from the selected item that has focus.
bigheadghost
Posts: 6
Joined: Tue Aug 15, 2017 2:31 am

Re: Inconsistent behaviors in custom open commands and context menu

Post by bigheadghost »

tested on 1.5.0.1411b x64

(2) single file (1.abc) selected:
pressing enter will execute the command. OK.
the default item in the context menu still remains "open with" of operating system, clicking it will do as the system, find app in microsoft store...
void
Developer
Posts: 19773
Joined: Fri Oct 16, 2009 11:31 pm

Re: Inconsistent behaviors in custom open commands and context menu

Post by void »

the default item in the context menu still remains "open with" of operating system, clicking it will do as the system, find app in microsoft store...
Thanks for checking 1411b.

I see, "Open with" is still shown in the menu, instead of Open when there's a custom open command.
Sorry I missed this.

I will look into showing the Open item when there's a custom open command.
void
Developer
Posts: 19773
Joined: Fri Oct 16, 2009 11:31 pm

Re: Inconsistent behaviors in custom open commands and context menu

Post by void »

Everything 1.5.0.1412b will now show Open when a custom open command is defined.
Post Reply