HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
matheusmoreira
.files
Shell2022–2026
matheusmoreira / .files

.files

No place like ~

2Distinct people
13Mentions
0Explicit recommenders
18GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

No place like ~

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 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 year13 dated mentions

Observed mentions: 2022-11-18 02:36:16 UTC to 2026-07-01 01:36:16 UTC.

02462022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC606

What Hacker News says

4 sources
It's mostly so I can immediately see which targets are phonies. Every phony has a line directly above it adding it to the list of phonies. When a makefile gets complex enough we need all the help we can get. I use phony targets so much I wrote a shell script to parse the makefile database dump into some sort of help text. It doesn't depend on that variable at all. https://github.com/matheusmoreira/.files/blob/master/~/.loca... Prints output like: phony1 phony2 dependency1 dependency2
In I Like Makefiles
Makefiles are an eerily lisplike turing tarpit. I hand wrote the makefiles for my projects, they generate wonderfully organized build trees. Hell I use makefiles to manage my dotfiles repository, even blogged about it. https://www.matheusmoreira.com/articles/managing-dotfiles-wi... The sanest way I've found to write makefiles is to think of it as a tool that maps input paths to output paths. When compiling a program, I want to map source/program.c to build/$(config)/objects/program.o so I write pattern rules that do just that. $(directories.build.objects)/%.o: $(directories.source)/%.c | directories $(strip $(CC) $(CFLAGS) -o $@ -c $<) Then I write make functions to convert paths in some tree to paths in another tree, which makes it easy to create lists of files which then match the pattern rules. source_to_object = $(patsu
Read the rest
bst $(directories.source)/%.c,$(directories.build.objects)/%.o,$(1)) These functions are then augmented by lots and lots of project specific variables to organize things... directories.source := source directories.build.root := build directories.build := $(directories.build.root)/$(config) directories.build.objects := $(directories.build)/objects sources.program := $(shell find $(directories.source) -type f) objects.program := $(call source_to_object,$(sources.program)) Then I add a real target which is supposed to get the makefile going. targets.program := $(directories.build)/program $(targets.program): $(objects.program) | directories $(strip $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^) Then I add a phony target for it. targets.phony += program program: $(targets.program) .PHONY: $(targets.phony) Then typing "make program" triggers the rule to make build/$(config)/program which depends on all the object files which will be linked into it which in turn is derived from a dynamically computed list of source files, and making those object files triggers the pattern rule which builds the entire thing. Using make without phony targets is insane. Without phony targets, I'd need to type things like "make build/aarch64/program" in order to get a build started. So I use phony targets for everything. Much easier to type "make program". It got to the point I created a phony-targets shell script which parses make's database output and processes it into a sort of help text for any given makefile's phony targets interface: https://github.com/matheusmoreira/.files/blob/master/~/.loca...
In I Like Makefiles
I (ab)use make to manage my dotfiles. https://github.com/matheusmoreira/.files/blob/master/GNUmake... I'm surprised at how well this thing works every time I use it. I even blogged about it. https://www.matheusmoreira.com/articles/managing-dotfiles-wi... Recently made a tool that processes the make database and prints the phony targets and their dependencies: https://github.com/matheusmoreira/.files/blob/master/~/.loca... I use it as a sort of makefile help command. Works surprisingly well too.
In How I stopped worrying and loved Makefiles

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.