⌘-K is Ctrl-L for the Terminal (I think): https://support.apple.com/guide/terminal/keyboard-shortcuts-...

The "open Terminal of selected folder" is the proper way, it requires a different workflow though, so I understand the issue in terms of muscle memory. An easy enough alternative (for me) is to drag and drop the current folder onto iTerm. When you have a folder open in Finder, and hover over the name of the Folder in the titlebar of the window, a blue "folder" icon appears. if you drag that to the iTerm icon in the dock and drop it, iTerm will activate and open a new terminal window in this folder.

Obviously, right-click is for losers and you just have to drag and drop the folder icon from the title bar onto the Terminal app icon.

/s

This is going to sound mental, but here you go. First enable the path bar in Finder by executing code provided to me by anonymous users on the internet: defaults write com.apple.finder ShowPathbar -bool true (EDIT: Apparently you can do CMD + OPT + P shortcut in Finder to accomplish the same)

Then in the path bar you can right click your current folder and open in Terminal (or use Services menu to open in 3rd-party terminals)

>I bought a thrown out M1 Macbook Air recently and I still haven’t figured out how to do a simple “right click in Finder > open Terminal here”

Right click -> Services -> New Terminal Tab at Folder

(or if you have Iterm: Right click -> Services -> New iTerm Tab/Window here)

Or if you have enabled Finder to show the path bar, right click on a folder in Path Bar (last one is the current open one) -> Open in Terminal

Then again, if you do work in the terminal, why do you navigate to the working directory via the UI Finder?

I also believe the project is struggling for an existence. From the readme:

> (Optional) Bind the ⌘-k hotkey

Just for people like me who don't tend to rtfm: after install, add the command `fzf_key_bindings` to your shell config to bind key combos.

Good question! This is complementary, not competitive, to the built-in fzf shortcuts. I use both cmdk and built-in fzf shortcuts in my day-to-day.

The concrete value-adds of cmdk (what fzf doesn't do out of the box):

1. Smart previews. You have to write the fzf preview command to preview text files, directories, images, PDFs, etc. cmdk gives you this out of the box (see https://github.com/mieubrisse/cmdk/blob/main/preview.sh ).

2. Choose the command for you. If you rely on the fzf Ctrl-T shortcut, you have to type the `cd`, the `vim`, the `open`, etc. I find that most of the time the command is predictable based on the filetype, so cmdk allows you to skip this (see https://github.com/mieubrisse/cmdk/blob/9d742112dab0475d7420... ). When cmdk doesn't have a command for the filetype though, I supplement with fzf's Ctrl-T.

3. Be smart about which files you're searching to be performant. E.g. very likely users aren't going to jump to files in the "~/Library/Application Support", or certain system directories under "/", so give users the option to go to the parent directory without crawling the subdirectories (see https://github.com/mieubrisse/cmdk/blob/main/list-files.sh ).