Skip to content

Conversation

@alfredomtx
Copy link
Contributor

Summary

Adds the AutoHotkey Debugger extension for Zed.

Features:

  • Debug AutoHotkey v1 scripts with breakpoints
  • Step through code (step in, step over, step out)
  • Variable inspection during debugging
  • Uses the autohotkey-debug-adapter DAP implementation

This complements the existing autohotkey tree-sitter extension (#4266) to provide a complete AutoHotkey development experience in Zed.

Repository: https://github.com/alfredomtx/zed-autohotkey-debugger
License: MIT

Adds syntax highlighting and comment toggling for AutoHotkey v1 (.ahk files).
Debug adapter for AutoHotkey v1 scripts with breakpoints, stepping,
and variable inspection. Complements the autohotkey tree-sitter extension.
@cla-bot cla-bot bot added the cla-signed label Dec 27, 2025
@MrSubidubi
Copy link
Member

Thanks for this! Is there any reason to not add this to the extension you want to add in #4266?

@alfredomtx
Copy link
Contributor Author

alfredomtx commented Dec 27, 2025

Thanks for this! Is there any reason to not add this to the extension you want to add in #4266?

Hi @MrSubidubi, just to keep as different repos, as they serve different purposes. Although they complement each other, it's easier to maintain/update

The .gitmodules file was missing several submodule entries that exist
in extensions.toml, causing CI validation to fail. Synced with upstream
main to include all missing entries including autumnal-marscape.
The autumnal-marscape submodule directory exists but was missing from
.gitmodules, causing CI validation to fail.
@alfredomtx
Copy link
Contributor Author

@MrSubidubi is there anything else pending to be able to merge?

@MrSubidubi
Copy link
Member

I think we would still prefer if you were to add this to the already published extension in an update - I do not really see what you mean by

it is easier to maintain/update

but feel free to elaborate on that, and we genreally prefer for extensions to provide as much as possible, especially for language extensions. They do serve different purposes, that said, only together will the experience be quite good for users. Also, we generally tend to ship debuggers with the language wherever we can and I'd honestly prefer if were were to not make this an exception here, especially given that you own the two repositories.

Feel free to provide arguments as well if you disagree, but how I currently see it, the cost of adding it to the other repository is minimal, as there is no Rust code involved so far, and everything could just go in a lib folder or whatever name you prefer there.

@alfredomtx
Copy link
Contributor Author

alfredomtx commented Jan 6, 2026

@MrSubidubi I had the "separation of concerns" mindset as my reason to keep it separated, and because the debugger repository is a fork of another repository. But I completely understand and agree with your point, for a language extension, it makes much more sense to have everything into one for a better user experience.

I'm closing this PR as I open a new one to update the main extension with the debugger merged into it, thank you for your attention, wish you a great day ☺️

Here's the PR to update the existing extension: #4383

@alfredomtx alfredomtx closed this Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants