Watching for File Changes on macOS
The article discusses how to monitor file changes on macOS using the File System Events API. It outlines the process of setting up an event stream to detect changes in source files for a local server with live reload functionality. The author shares insights on building a Swift script to utilize the FSEvents API and connect it with Python for further processing.
- ▪The File System Events API allows for passive monitoring of file changes in macOS.
- ▪The author previously used Jekyll's livereload feature and is now creating a similar functionality for their own static site generator.
- ▪The article provides a step-by-step guide on creating a file systems event stream using FSEventStreamCreate.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Alexwlchan |
| Canonical URL | https://alexwlchan.net/2026/watch-files-on-macos/ |
| Publication time | Sun, 24 May 2026 06:39:15 +0000 |
| Retrieval time | 2026-05-24T07:07:31.109Z |
| Last seen | 2026-05-24T07:07:31.109Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 471XGSbTFWVC |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Watching for file changes on macOSPosted 11 May 2026Also filed in Swift, Blogging about bloggingWhen I’m working on this website, I want a local server with live reload. I want to be able to open the site in my web browser, make changes to the source files, and have my browser automatically refresh the page when the site is updated. I use this whenever I’m working on the site, and I find it helpful to see my writing in a different font/layout to my text editor; I spot lots of typos and mistakes that way.When I was using Jekyll, I used the command jekyll serve --livereload. Now I’ve written my own static site generator, I need to build my own version.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Alexwlchan.
Discussion
0 commentsMore from Alexwlchan
