
Article URL: https://www.ycombinator.com/companies/proprise/jobs/ppipLUK-founding-engineer
Comments URL: https://news.ycombinator.com/item?id=43150885
Points: 0
# Comments: 0
https://www.ycombinator.com/companies/proprise/jobs/ppipLUK-founding-engineer

Article URL: https://github.com/vinceliuice/WhiteSur-gtk-theme
Comments URL: https://news.ycombinator.com/item?id=43151294
Points: 138
# Comments: 85

Article URL: https://www.sciencefriday.com/articles/doctored-book-excerpt/
Comments URL: https://news.ycombinator.com/item?id=43151320
Points: 71
# Comments: 12
https://www.sciencefriday.com/articles/doctored-book-excerpt/
Article URL: https://onlinesafetyact.co.uk/in_memoriam/
Comments URL: https://news.ycombinator.com/item?id=43152154
Points: 140
# Comments: 56



Article URL: https://ukdataexplorer.com/european-translator/
Comments URL: https://news.ycombinator.com/item?id=43152587
Points: 20
# Comments: 3

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 synt
Article URL: https://sifted.eu/articles/eu-startup-regulation-2025
Comments URL: https://news.ycombinator.com/item?id=43152937
Points: 16
# Comments: 0
Article URL: https://news.ycombinator.com/flagged
Comments URL: https://news.ycombinator.com/item?id=43149186
Points: 68
# Comments: 42