Skip to content
Lanterna

Usage

Basic operation, filtering, window actions, links, and troubleshooting

  1. 01 Hold⌘Keep holding Cmd
  2. 02 StepTab× nPress Tab for the next window
  3. 03 Release⌘Release Cmd to switch
⌘Tab Shows the switcher. Keep holding Cmd and press Tab to move, then release Cmd to switch.
⇧⌘Tab Moves in the reverse direction.
  1. 01 Open⌘SpaceOpen in filter mode
  2. 02 TypeA–ZType to narrow the list
  3. 03 Switch↩Switch to the chosen window
⌘Space Shows the switcher in filter mode. In this mode, releasing Cmd does not close it. Pressing it in a switcher opened with Cmd+Tab switches that switcher to filter mode.
A–Z Keeps only the rows whose app name or window title contains what you typed. Case is ignored.
↑↓ Moves the selection.
↩ Switches to the chosen window.
⌫ Deletes one character.
esc Clears what you typed. With nothing typed, closes the switcher.

Filter input also matches romaji. For example, gijiroku matches ぎじろく and 議事録. Kana readings work with the bundled tables. Kanji readings need a dictionary.

To match kanji readings, place a migemo-dict file next to the config file and relaunch Lanterna.

Terminal window
curl -L -o SKK-JISYO.L https://raw.githubusercontent.com/skk-dev/dict/master/SKK-JISYO.L
curl -L -o skk2migemo.sh https://raw.githubusercontent.com/peacock0803sz/Lanterna/main/scripts/skk2migemo.sh
bash skk2migemo.sh SKK-JISYO.L ~/Library/Application\ Support/Lanterna/migemo-dict

SKK dictionaries ship in EUC-JP, so the script converts the output to UTF-8. Entries with okurigana are out of scope, /-separated candidates become tab-separated words, and annotations after ; are dropped, keeping bare kanji only. With a repo checkout, use scripts/skk2migemo.sh directly.

While the switcher is up, hold Cmd and press one of these keys to act on the chosen row. The switcher stays up and the list updates in place.

⌘W Closes the window.
⌘Q Quits the app.
⌘H Hides the app.
⌘M Minimizes the window.

By default, hidden apps and minimized windows move below the other windows, grouped under headings such as HIDDEN APPS and MINIMIZED. If an action fails, the list goes back to how it was and a short note appears. You cannot act on Lanterna’s own row.

Every keybinding below can be changed through the keybindings section of the config file or the Keyboard tab of Settings. Keys are physical positions, so they work the same under any input source.

Action Default keys
Show ⌘Tab
Show in reverse ⇧⌘Tab
Show for filtering ⌘Space
Next ↓
Previous ↑
Commit ↩, keypad Enter
Cancel esc, ⌘.
Delete backward ⌫
Clear query esc
Close window ⌘W
Quit application ⌘Q
Hide application ⌘H
Minimize window ⌘M

Show, Show in reverse, and Show for filtering reach across the system, and the window actions would fire while typing, so every key for those needs Cmd, Ctrl, or Opt. A key already used by another action is refused, except that Clear query and Cancel may share keys. An action left with no keys falls back to its defaults, but if the defaults are also taken the action can stay unbound with a diagnostics entry. Invocation changes apply at once.

Cmd+Tab shortcuts are not restored after a crash

Section titled “Cmd+Tab shortcuts are not restored after a crash”

Lanterna takes Cmd+Tab and Shift+Cmd+Tab away from the system while it runs and gives them back when it exits. After kill -9 or a crash it cannot give them back, so both shortcuts stay off until something else restores them.

Check that no Lanterna is running before doing anything else. Restoring turns the shortcuts back on without reading their current state, so running this while another Lanterna is up takes the shortcuts away from that process. Running more than one at a time is not supported.

Terminal window
pgrep -x Lanterna # expect no output; run `pkill Lanterna` first if there is any

Then start Lanterna again and stop it cleanly, so its shutdown restores the shortcuts.

Terminal window
/Applications/Lanterna.app/Contents/MacOS/Lanterna &
sleep 1
pkill Lanterna

If the shortcuts are still off after that, log out and back in. The system’s assignment is per login session.

Check that Accessibility and Input Monitoring are granted (see the Guide), then relaunch Lanterna.

If these steps do not fix the problem, please open a bug report using the Bug report template.