Explore in Everything context menu item

[void]

Explore in Everything will open the specified folder in the folder sidebar.
The folder sidebar is shown if it is currently not visible when exploring in Everything.



To create an "Explore in Everything" context menu item (when right clicking a folder):

• From the Start menu, search for: regedit
• Right click Registry Editor and click Run as administrator.
• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Folder\shell

• Create a new key called:

  Code: Select all

  Explore in Everything...

• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Folder\shell\Explore in Everything...

• Create a new key called:

  Code: Select all

  command

• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Folder\shell\Explore in Everything...\command

• Set the (Default) value to:

  Code: Select all

  "C:\Program Files\Everything\Everything64.exe" -explore "%1"

  where C:\Program Files\Everything\Everything64.exe is the location of your Everything.exe.

To create an "Explore in Everything" context menu item (when right clicking inside a folder on the background):

• From the Start menu, search for: regedit
• Right click Registry Editor and click Run as administrator.
• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Directory\Background\shell

• Create a new key called:

  Code: Select all

  Explore in Everything...

• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Directory\Background\shell\Explore in Everything...

• Create a new key called:

  Code: Select all

  command

• Navigate to:

  Code: Select all

  HKEY_CLASSES_ROOT\Directory\Background\shell\Explore in Everything...\command

• Set the (Default) value to:

  Code: Select all

  "C:\Program Files\Everything\Everything64.exe" -explore "%V"

  where C:\Program Files\Everything\Everything64.exe is the location of your Everything.exe.

[therube]

You can do something similar, opening the directory that a file is within.

Code: Select all

REGEDIT4

[HKEY_CLASSES_ROOT\*\shell\EverythingSearch File Parent Folder]

[HKEY_CLASSES_ROOT\*\shell\EverythingSearch File Parent Folder\command]
@="C:\\DEV\\Locate\\15.1337\\Everything.exe -instance 15 -parentpath \"%1\""

I called it "EverythingSearch File Parent Folder". (Not very good, but whatever.)
And of course you'll need to change the path to Everything.exe to fit your needs.


(Do backup your Registry, in case.)

[void]

Replace -parentpath with -explore if you want to explore the specified folder in the folder sidebar.



Added Explore in Everything clarification.
Currently, there's no UI option to install the Explore in Everything context menu.



Added folder background "Explore in Everything" context menu item install instructions.



To install/uninstall the "Search in Everything" folder context menu, please see:
Show folder context menus
Search Everything... folder context menu item

[tuska]

You can do something similar, opening the directory that a file is within.
...

Hi,

I would like to implement this using

Code: Select all

C:\Everything\Everything64.exe

Unfortunately, my attempt failed, because the entry (crossed out in the picture) is in the wrong place and maybe not correct(?) otherwise.
The command is the same as for the context menu item: "Explore in Everything..." (changed from me to: -parentpath)

Code: Select all

"C:\Everything\Everything64.exe" -parentpath "%1"

I have created the entries manually in the registry with the instructions in the first post - now probably in the wrong folder.
 

2023-02-17_Explore File Parent Folder in Everything.png (18.77 KiB) Viewed 11558 times

 
This is my attempt at an adaptation to my path and text for the context menu entry.
If this is correct, I still don't know how to do an import into the registry.
Maybe save the code as a .reg file and double click on the file to start the import?

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\Explore File Parent Folder in Everything...]

[HKEY_CLASSES_ROOT\*\shell\Explore File Parent Folder in Everything...\command]
@="C:\\Everything\\Everything64.exe -parentpath \"%1\""

Please help me with the exact path -> *\ = ??.
I am interested in this because I need to know the location in the registry in case I change the Everything command line parameter (to: -explore).

EDIT:
Based on subsequent forum posts, I eventually made this change:

Code: Select all

FROM: REGEDIT4
TO  : Windows Registry Editor Version 5.00

/EDIT

[NotNull]

This is mostly correct, but indeed the wrong location: it is now under HKCR\Folder in the registry.

For files there is a differnt part of the registry. You could add this to a specific file extension (let's say jpg files), but for all files there is a registry entry HKCR\*


Here an export of my quick test (with different paths).

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\Shell\Search file's folder in Everything]
"Icon"="\"C:\\Program Files\\Everything 1.5a\\Everything64.exe\""

[HKEY_CLASSES_ROOT\*\Shell\Search file's folder in Everything\command]
@="\"C:\\Program Files\\Everything 1.5a\\Everything64.exe\" -parentpath \"%1\""

[therube]

Your .reg looks good.

If this is correct, I still don't know how to do an import into the registry.
Maybe save the code as a .reg file and double click on the file to start the import?

Double-click should work. Or Right-click the .reg, & Merge (would accomplish the same).
.

Everything Search a Files Parent Directory.png (23.03 KiB) Viewed 11537 times

(I've mentioned 1 & 2 before. So now I throw in a 3 .
me, notnull, tuska)

[NotNull]

Your .reg looks good.

Thank you!! I'm glad you noticed. Polished it for almost an hour with reg-cleaner 3.0

I know you meant @tuska's .reg ...
TBH, I didn't check that (just the pictures), but it looks very similar to what I posted. Should work.

[tuska]

2therube
2NotNull

Thank you very much for your prompt support!
I have now successfully set it up for FILES(!).
(The * in the path had completely confused me, as I thought it was a placeholder).
 

2023-02-17_Explore in Everything context menu item_FILES.png (124.58 KiB) Viewed 10921 times

 
EDIT:
Based on subsequent forum posts, I eventually made this change:
Code change...

Code: Select all

FROM: REGEDIT4
TO  : Windows Registry Editor Version 5.00

... and code for ICON added.
/EDIT

[NotNull]

FWIW: Check the regfile I posted to see how to add an icon to the context menu entry.

[tuska]

FWIW: Check the regfile I posted to see how to add an icon to the context menu entry.

Thank you, I had already noticed it.
I revised the .reg file again and then overwrote the registry entry by double-clicking on the .reg file.

This is now my final .reg file (for "C:\Everything\Everything64.exe"):

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\Explore File Parent Folder in Everything...]
"Icon"="\"C:\\Everything\\Everything64.exe\""

[HKEY_CLASSES_ROOT\*\shell\Explore File Parent Folder in Everything...\command]
@="C:\\Everything\\Everything64.exe -parentpath \"%1\""

2023-02-17_Icon for Everything context menu item.png (1.68 KiB) Viewed 11519 times

 
PS:
For the "Explore in Everything..." context menu entry, I also manually entered the icon in the registry.

EDIT:
Based on subsequent forum posts, I eventually made this change:

Code: Select all

FROM: REGEDIT4
TO  : Windows Registry Editor Version 5.00

/EDIT

[NotNull]

Should have known you knew that already....

[horst.epp]

Im wondering about the first line of the reg file.
Shouldn't it be
Windows Registry Editor Version 5.00

[tuska]

Im wondering about the first line of the reg file.
Shouldn't it be
Windows Registry Editor Version 5.00

If one makes an registry export, then this info is in the .reg file: Windows Registry Editor Version 5.00
However, I had not dared to change the code provided by therube, because I couldn't assess the possible impact.
The code also works fine.

I'm still unsure if I should adjust my posts above with code.
______________________________________________________
Windows 11 Pro (x64) Version 22H2 (OS build Build 22621.1265)

[horst.epp]

Im wondering about the first line of the reg file.
Shouldn't it be
Windows Registry Editor Version 5.00

If one makes an registry export, then this info is in the .reg file: Windows Registry Editor Version 5.00
However, I had not dared to change the code provided by therube, because I couldn't assess the possible impact.
The code also works fine.

I'm still unsure if I should adjust my posts above with code.
______________________________________________________
Windows 11 Pro (x64) Version 22H2 (OS build Build 22621.1265)

All reg files found on my system even from 3rd party providers have the version 5 header.

[NotNull]

"Internet" says REGEDIT4 is oldskool is for ANSI .reg files (doesn't support unicode)
On a halfway modern system (post Windows 98/NT4) better use the default "Windows Registry Editor Version 5.00"

But maybe @therube has a specific reason for REGEDIT4?

[Michi]

So, any chance that those settings will find their way into the preferences of ET sometime, without tinkering in the Registry?
Would be much easier for some of us

[therube]

If you save of of the "[ code ]" files as filename.reg, you can simply double-click that file, & you'll be asked to import it into the Widows Registry.

You would need to "tweak" things to meet your needs, as appropriate (paths, instances & whatnot).

(So I guess in that sense, it still isn't quite "clear cut".)

[therube]

specific reason for REGEDIT4

My default viewer (F3 in Salamander) displays REGEDIT4 correctly, where REGEDIT5 looks like gibberish (i.e., I guess it does not handle "unicode"), so when I export I select Win9x/NT4 .reg format. No other reason.

[tuska]

If one makes an registry export, then this info is in the .reg file: Windows Registry Editor Version 5.00
However, I had not dared to change the code provided by therube, because I couldn't assess the possible impact.
The code also works fine.

I'm still unsure if I should adjust my posts above with code.

specific reason for REGEDIT4

My default viewer (F3 in Salamander) displays REGEDIT4 correctly, where REGEDIT5 looks like gibberish
(i.e., I guess it does not handle "unicode"), so when I export I select Win9x/NT4 .reg format. No other reason.

2therube
Thank you for your information and your efforts!

I will leave my presentation (image and code) above unchanged, as this code works perfectly.
Thus, every user has the choice of entering either

REGEDIT4

or

Windows Registry Editor Version 5.00

in the first line of the code.

[horst.epp]

I will leave my presentation (image and code) above unchanged, as this code works perfectly.
Thus, every user has the choice of entering either

REGEDIT4

or

Windows Registry Editor Version 5.00

in the first line of the code.

This is only true as long as no Unicode characters are necessary.

[tuska]

I will leave my presentation (image and code) above unchanged, as this code works perfectly.
Thus, every user has the choice of entering either

REGEDIT4

or

Windows Registry Editor Version 5.00

in the first line of the code.

This is only true as long as no Unicode characters are necessary.

Because of your contribution, I have now changed my mind again and have edited my contributions above (including image correction)
to the following:

EDIT:
Based on subsequent forum posts, I eventually made this change:

Code: Select all

FROM: REGEDIT4
TO  : Windows Registry Editor Version 5.00

... and code for ICON added.
/EDIT

Thank you!

[therube]

I'll note that if you use multiple instances (Everything.exe -instance blablabla), the Registry entry is only set to open a specific instance.

The "instance name" (or lack thereof) is "hardcoded" in the Registry entry.
So if you're working in a different instance from that noted in the Registry, using this context-menu method will result in that instance being opened, rather then the particular instance you're invoking the command from.


I suppose there is no way around that?

[void]

Only one Search Everything folder context menu item can be installed from Tools -> Options -> General -> Show Search Everything folder context menu item.



To manually add another folder context menu item:

• From the Start menu, search for:
  regedit
• Right click Registry Editor and click Run as administrator.
• In the Registry Editor, navigate to:
  HKEY_CLASSES_ROOT\Directory\shell
• Create a New key called:
  Search Everything (My Instance Name)
• Navigate to:
  HKEY_CLASSES_ROOT\Directory\shell\Search Everything (My Instance Name)
• Create a New key called:
  command
• On the right, set the (Default) value data to:
  "C:\Program Files\Everything\Everything.exe" -path "%1" -instance "My Instance Name"