search

e-dant / watcher

Filesystem watcher. Works anywhere. Simple, efficient and friendly.
MIT License
639 stars 32 forks source link

`include` Directory Conventions #2

Closed e-dant closed 1 year ago

e-dant commented 1 year ago

Decide which one you want:

e-dant commented 1 year ago

Leaning towards the shallow include because it fits better with the philosophy that every directory should have a readme.

e-dant commented 1 year ago

The stuttering include is used more often and is probably easier for users who just want to cp -r include/watcher.

A single-header build target could be created to amalgamate and place a build/out/watcher.hpp file. But should this even be a build target? Wouldn't this be a bit confusing? For package managers, this may be easier to distribute.

Perhaps we should repurpose the include/watcher/watcher.hpp to be an amalgamation made from a pre-commit .hooks/pre-commit stub pointing to tool/shone.

The existing watcher.hpp could be renamed: run.hpp, which is the function it provides.

e-dant commented 1 year ago

https://github.com/e-dant/watcher/commit/d0431f54e3f45e976a5fe1bb9e90c542e8ede797