cmderdev / cmderdev/cmder

Question: How to use Cmder with AutoHotkey?

Open
#2,982 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

❔ Type: Question
Dominant language
PowerShell
Stars
27k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Description

Question

I don't know if this is a question or rather a bug. Pardon me if it's in the wrong place.

I have an AutoHotkey V2 script always running in the background, whose main function is to map the Caps Lock key to act as a modifier (link for reference). The problem is that, more often than not, Cmder completely ignores the script, and this behavior even propagates to the programs opened from Cmder. For example, if Cmder ignores the script and I run VS Code from it, VS Code ignores the AutoHotkey script as well. However, if I open VS Code normally (not from Cmder), it works as expected.

Sometimes, when I restart my PC or Cmder, it works and captures the AutoHotkey script, but I still haven't found the situation that triggers this issue.

If anyone can shed some light on this, I'd be happy to hear it.

Cmder version: Version 1.3.24.236
Operating system: Windows 11

Checklist
  • I have read the documentation and made sure what I'm looking for isn't present, or is unclear.
  • I have searched for similar issues, and either this question wasn't asked before, or I didn't find any that describe my question.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior on Windows 11 with Cmder 1.3.24.236 and the linked AutoHotkey V2 script. Compare AutoHotkey input handling when VS Code is launched from Cmder versus normally, and document a reliable trigger or confirmed explanation for the difference.

Written by the indexing model from the issue text.

Assessment

Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.