kutlime / powershell-open-here-module Goto Github PK

This command is same for both
\HKEY_CLASSES_ROOT\Directory\ContextMenus\Terminal\shell\runas\command
and
\HKEY_CLASSES_ROOT\Directory\ContextMenus\Terminal\shell\openterminal\command

And runas command also doesn't work at all

In this article for adding Bash to the context menu, author provides two registry keys with just a single 2-character difference effectively.

https://www.tenforums.com/tutorials/60125-open-bash-window-here-context-menu-add-windows-10-a.html

Should be easy to add a command-line parameter to give people the option to have these menus only available under shift-rightclick. This would be nice to avoid polluting default shells.

Registry keys are available here:

https://www.tenforums.com/tutorials/60125-open-bash-window-here-context-menu-add-windows-10-a.html

The goal of this enhancement is:

1. Provide PowerShell Core custom shortcut experience.
2. Provide a possibility to create the PowerShell Core shortcut after PowerShell Core installation without a need to reinstall it.

I noticed after add open here in Windows terminal, one powershell window will prompt first. It would be better if windows terminal can be launched directly.

when i click "Open here" and I had a window open earlier, i hope they all open in a window.
in other words, when i click "Open here" twice, they are both in a window

↑ this is NOT what i want

↑ this is what i want

I tried this expecting them to all show up under a single root. Instead, they all created their own duplicate root item called "Prompts". Can the desired behavior be supported?

Set-OpenHereShortcut -ShortcutType:Windowsterminal -RootName 'Prompts' -OpenHere 'Terminal' -OpenHereAsAdmin 'Terminal as Admin'
Set-OpenHereShortcut -ShortcutType:WindowsPowerShell -RootName 'Prompts' -OpenHere 'Powershell' -OpenHereAsAdmin 'Powershell as Admin'
Set-OpenHereShortcut -ShortcutType:CMD -RootName 'Prompts' -OpenHere 'CMD' -OpenHereAsAdmin 'CMD as Admin'

Try `Set-OpenHereShortcut -ShortcutType:WindowsTerminalPreview" but wrong.

The goal of this enhancement is:

1. Provide PowerShell Core custom shortcut
2. Provide a possibility to create the PowerShell Core shortcut after PowerShell Core installation without a need to reinstall it.

Related issue: #11

The extra click to expand the menu to get to an admin-level context menu item seems to be unavoidable with the current options.

It seems that flexibility would be greatly enhanced by generalizing this solution to be able to specify that you are trying to create a top-level item rather than something in a expanding menu.

Hi,
is it possible to use this to open a specific profile (i.e. not the default profile) in Windows Terminal?
For example, my default profile is the WSL Bash, but I would like to open a powershell tab in Windows Terminal.
Thanks

The current approach of icon handling is to create a folder in LOCALDATA, download the shell's icon from the GitHub repository or create the icon when download fails from a base64 string.

The new approach will use EXE icon by default, brings a new switch -UseCustomIcon to the Set-OpenHereShortcut. The current approach will be used when -UseCustomIcon will be present in a SetOpenHereShortcut call.