ABabound·Feb 28, 2025
I think mdq [1], which was recently on HN somewhere, fits this.
[1] https://github.com/yshavit/mdq
In Calendar.txtyshavit
mdq
Rust2025–2025
yshavit / mdq
mdq
like jq but for Markdown: find specific elements in a md doc
2Distinct people
2Mentions
0Explicit recommenders
1.7KGitHub stars
What to know before exploring
What it is
like jq but for Markdown: find specific elements in a md doc
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 6-hour interval2 dated mentions
Observed mentions: 2025-02-23 20:05:49 UTC to 2025-02-28 16:36:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Feb 23, 18:00 | 2025-02-23 18:00:00 UTC | 2025-02-24 00:00:00 UTC | 1 | 1 | 0 |
| Feb 24, 00:00 | 2025-02-24 00:00:00 UTC | 2025-02-24 06:00:00 UTC | 0 | 0 | 0 |
| Feb 24, 06:00 | 2025-02-24 06:00:00 UTC | 2025-02-24 12:00:00 UTC | 0 | 0 | 0 |
| Feb 24, 12:00 | 2025-02-24 12:00:00 UTC | 2025-02-24 18:00:00 UTC | 0 | 0 | 0 |
| Feb 24, 18:00 | 2025-02-24 18:00:00 UTC | 2025-02-25 00:00:00 UTC | 0 | 0 | 0 |
| Feb 25, 00:00 | 2025-02-25 00:00:00 UTC | 2025-02-25 06:00:00 UTC | 0 | 0 | 0 |
| Feb 25, 06:00 | 2025-02-25 06:00:00 UTC | 2025-02-25 12:00:00 UTC | 0 | 0 | 0 |
| Feb 25, 12:00 | 2025-02-25 12:00:00 UTC | 2025-02-25 18:00:00 UTC | 0 | 0 | 0 |
| Feb 25, 18:00 | 2025-02-25 18:00:00 UTC | 2025-02-26 00:00:00 UTC | 0 | 0 | 0 |
| Feb 26, 00:00 | 2025-02-26 00:00:00 UTC | 2025-02-26 06:00:00 UTC | 0 | 0 | 0 |
| Feb 26, 06:00 | 2025-02-26 06:00:00 UTC | 2025-02-26 12:00:00 UTC | 0 | 0 | 0 |
| Feb 26, 12:00 | 2025-02-26 12:00:00 UTC | 2025-02-26 18:00:00 UTC | 0 | 0 | 0 |
| Feb 26, 18:00 | 2025-02-26 18:00:00 UTC | 2025-02-27 00:00:00 UTC | 0 | 0 | 0 |
| Feb 27, 00:00 | 2025-02-27 00:00:00 UTC | 2025-02-27 06:00:00 UTC | 0 | 0 | 0 |
| Feb 27, 06:00 | 2025-02-27 06:00:00 UTC | 2025-02-27 12:00:00 UTC | 0 | 0 | 0 |
| Feb 27, 12:00 | 2025-02-27 12:00:00 UTC | 2025-02-27 18:00:00 UTC | 0 | 0 | 0 |
| Feb 27, 18:00 | 2025-02-27 18:00:00 UTC | 2025-02-28 00:00:00 UTC | 0 | 0 | 0 |
| Feb 28, 00:00 | 2025-02-28 00:00:00 UTC | 2025-02-28 06:00:00 UTC | 0 | 0 | 0 |
| Feb 28, 06:00 | 2025-02-28 06:00:00 UTC | 2025-02-28 12:00:00 UTC | 0 | 0 | 0 |
| Feb 28, 12:00 | 2025-02-28 12:00:00 UTC | 2025-02-28 18:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesShow HN: Jq-Like Tool for Markdown
There have been a few times I wanted the ability to select some text out of a Markdown doc. For example, a GitHub CI check to ensure that PRs / issues / etc are properly formatted.
This can be done to some extent with regex, but those expressions are brittle and hard to read or edit later. mdq uses a familiar pipe syntax to navigate the Markdown in a structured way.
It's in 0.x because I don't want to fully commit to the syntax being stable, in case real-world testing shows that the syntax needs tweaking. But I think the project is in a pretty good spot overall, and would be interested in feedback!
325 points · Open discussion