The releases are named evangelion and miasma, and the documented setup clones a plugin into a tilde
rice ๐ custom linux config files. as seen on r/unixporn #noricenolife neovim cultist. dotfiles are perpetual wip
At a glance
- What is it?
- xero/dotfiles is a personal Linux configuration managed with GNU Stow, covering shell, terminal, tmux, editor, version control and signing keys, plus a setup script for a fresh server. It is honest about being a work in progress and unusually explicit about the one thing that breaks Stow installs, but its release tags carry no version numbers and its copy-paste setup block has a typo that will create a directory called with a tilde in it.
- Who is it for?
- Use this repository as a worked example of Stow, because the readme explains the symlink farm properly, including the failure everyone hits once, and because the directory layout shows what a terminal-first configuration actually contains. Three things to know before you adopt it.
- Can I use it commercially?
- Yes. CC0-1.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 118 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- xero/dotfiles2,398 โ ยท +10
| Repository | 2026-09-29 | 2026-11-15 |
|---|---|---|
| xero/dotfiles | 2.4k | 2.4k |
10 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The release tags are named, so there is no version to pin
Two releases are visible and neither has a number in its name.
One is tagged with a word from an anime series, published in March 2025. The other is tagged with another word, published in August 2024. There is no semantic version, no patch level, and nothing in either tag that tells you what changed or what it is compatible with.
For a repository that publishes configuration rather than code, that is a defensible choice. A version number implies a compatibility promise, and a shell configuration has a different kind of compatibility surface: it depends on the programs it configures, not on an API. A tag that names a look or a mood is honest about that.
It is still inconvenient in one specific way. If you follow the readme's advice and keep a checkout of this repository as the source for your symlink farm, there is no way to ask what you had last March other than looking at dates. The last push to the default branch is 2026-07-20, four months after the newer tag, so the branch has moved on without a release.
The repository description also describes itself as a perpetual work in progress, which is at least consistent with the tagging policy: nobody is promising that a tag means anything stable.
Stow's one real gotcha is documented in the readme
The installation mechanism is GNU Stow, described as a free, portable, lightweight symlink farm manager, and the readme is clear about why: it lets a versioned directory of configuration be linked into place with one command, which makes the same set shareable between machines and between users, and it keeps version control files out of the home directory itself.
The library is installed through a package manager on every distribution the readme names, with five commands covering the Debian family, Homebrew, the Fedora family, Arch and the Red Hat family. Building it from source is the alternative.
The mechanism is explained properly, which is more than most dotfile repositories do. Stow, by default, links files from the parent directory of wherever you run it, which is why the author keeps the repository in a specific location and passes an explicit target on every command. Without the target flag, the links end up one directory deeper than intended. The readme gives the concrete example: linking the shell folder links a dotfile into the shell configuration directory, and linking the scripts folder with a target of the local binary directory links a script named `food` there, because Stow reproduces the repository's own directory layout rather than flattening it. That single sentence explains why the scripts live one level deeper inside the repository than you would expect.
And then there is the gotcha, in bold in the original: Stow can only create a symlink if the destination file does not already exist. If a program wrote a default configuration file when it was installed, you have to delete it before linking your own. The readme notes this applies to files only, not directories, and links an issue for the rest.
The setup block clones the editor plugin into a path that does not exist
The readme offers a one-shot alternative to running the commands by hand: a setup script in the repository, or something like it. The pasted version is a shell block with three sections, and the third one has a mistake.
The first section clones the repository into a versioned location, changes into it, and links eight folders at once with the home directory as the target: the scripts, the shell, the version control, the signing keys, the secure shell, the terminal multiplexer, the editor and the interactive shell. That part is correct and matches the explanation above.
The second section installs a plugin manager for the terminal multiplexer, shallow-clones it, runs its installer script, changes into a specific plugin and drives its installer with an automation tool, sending a carriage return twice and waiting for it to finish. That is a reasonable way to answer an interactive prompt from a script, and it is the part of the setup most likely to break first when that plugin's prompts change.
The third section is the problem. It creates a directory for the editor's plugin data, and then clones the plugin manager into a path consisting of a single tilde character, at the end of the command. A tilde is expanded by the shell to your home directory, so the clone target is your home directory, and a clone into an existing non-empty directory does not do what a fresh clone into a named directory does. As written it will either fail or leave the plugin somewhere you did not intend.
The block also mixes tabs and spaces for indentation in consecutive lines, which is harmless to the shell and a hint that it was assembled rather than tested as a unit.
The main branch is terminal-only, and the tree still has window manager files
The first note on the page is a retraction, and it is the most useful paragraph in the readme.
The window manager configurations, with two specific tiling window managers named and their branch linked, now live on a separate branch and are not actively maintained, because the author no longer uses a graphical session. The words used are that they live in the terminal now, free of the display server.
So the default branch is a terminal configuration, and the graphical one is preserved rather than deleted, on a branch the note points you to. That is the right way to do it: the history is intact, the default branch matches current practice, and anyone still running a tiling window manager knows where to look.
What is worth noting is that the default branch's tree does not match that description cleanly. Alongside the shell, terminal, multiplexer, editor, version control, signing key and secure shell directories, it still contains a directory for an X display server configuration, a wallpaper directory, a directory for a graphical wrapper around the editor, and a directory of miscellaneous shell scripts. Those are the leftovers of the earlier setup, and the note does not claim they are unused.
It is a small inconsistency in a repository whose author is otherwise candid about scope. Nothing is broken by it, but a reader deciding whether this configuration suits them will find both eras represented on the same branch.
Two supported layouts, and the awkward one is the documented default
There are two ways to arrange this repository on your machine, and the readme supports both.
The first is what the author does: keep the checkout in a hidden, nested location, and pass a target flag on every Stow command so the links land in the home directory rather than beside the checkout. The readme is explicit about the consequence of getting this wrong, which is that the links end up in the wrong directory. The command for the shell configuration looks like this:
stow zsh -t ~and the readme says that links a dotfile into the shell configuration directory.
The second is the convenience route: clone into a directory directly under your home directory, and then run the same commands with no flags at all, because Stow's default target becomes the parent directory, which is the home directory you wanted. The readme offers this as the easier option and then immediately undercuts it with a joke about nobody liking things to be easy in this world.
The summary section at the bottom of the readme then gives the convenience route as five separate steps: change to your home directory, clone, change into the new directory, link the shell folder, and, if you want the same for the root account, run the same command with a target of the root home directory. Uninstalling is a single command with a flag that means do the reverse.
So both layouts are real and both are documented, and the summary is the one a newcomer will follow. That is the right default: the awkward layout is a preference, and the readme says so rather than pretending otherwise.
The terminal setup is a tablet, a mobile shell and an encrypted connection
The section on the terminal emulator is the shortest one and explains the whole configuration at once.
The author has been using an eleven-inch tablet with a laptop processor generation and a bluetooth keyboard at sixty-eight percent size as the main computer, and runs the community edition of a mobile-focused terminal emulator on it, connected to a server. Fonts are a well-known monospace one, with a patched build that adds extra icons for extended unicode and emoji, and both the font and the colour schemes are stored inside the repository as base64-encoded stylesheet data rather than as font files.
The configuration routine is described as a single menu action under appearance, then setting the screen mode, then supplying a server identity and keys. After that there is exactly one command, and it is a mobile shell invocation against a server alias.
That is a specific and demanding setup: a tablet as the only machine, a terminal emulator that is not a terminal emulator, and a persistent server somewhere else. It explains a good deal about the rest of the repository, particularly why the multiplexer, the editor plugin manager and the secure shell configuration are as heavily configured as they are, and why the graphics-era directories are vestigial.
The server section follows the same logic, naming a particular Linux release on a particular cloud provider, and pointing at a setup script in the repository that installs packages, tools and services, creates a user and sets up keys.
The licence is a public domain dedication
The repository is dedicated to the public domain under a Creative Commons zero-style dedication, and that is worth a paragraph because it is unusual for a dotfile repository.
Most configuration repositories use a permissive licence with an attribution clause, which means anyone reusing your shell configuration has to keep your name on it. A public domain dedication removes that requirement. There is nothing to preserve, nothing to attribute and nothing to ask permission for, and the reuse terms are the most permissive available.
For a repository whose stated purpose is being copied, that is the correct choice and a considerate one. A shell configuration is not much use sitting in one person's home directory, and a licence that makes copying frictionless is more useful to the person who wrote it than a licence that makes copying conditional.
The homepage recorded for the repository is a plain HTTP short link, which is the one small thing on the page that works against the spirit of a licence written to be maximally permissive: the file you are pointed at is fetched over an unencrypted connection. The readme's banner also names a second address, over HTTP, for the code, alongside an encrypted one for the mirror.
The readme explains what a dotfile is before explaining how to install one
The first prose section of the readme is a definition, and it is worth keeping in mind before reading the rest as instructions.
Programs in this world are configured two ways, through shell arguments or through text files, and programs with many options, text editors being the example given, are configured per user with files in the home directory. In unix-like systems any name beginning with a period is treated as hidden and is not displayed in a default view, which is where the word comes from.
The readme then names the maxim that console users live by, that you are your dotfiles, and explains why the files get backed up and shared: for the people who post their desktops and for the people who post their terminals, these files matter. It adds the specific difficulty that anyone creating custom themes faces, which is managing several versions of them.
What follows is an argument for a tool. The author says they have tried many ways of organising this, and asks the reader to take their word for it that keeping a version control repository in the root of your home directory is a bad idea. They have written shell scripts to move or link files into place. There are existing dotfile managers, the readme says, but they all seem to carry a lot of dependencies. And then the conclusion: there had to be a simple tool for this.
That paragraph is the real introduction to the repository. Everything after it is the answer to a problem the author had, which is also the reason this repository is more useful than a screenshot.
Editorial conclusion
Use this repository as a worked example of Stow, because the readme explains the symlink farm properly, including the failure everyone hits once, and because the directory layout shows what a terminal-first configuration actually contains. Three things to know before you adopt it. That it is one person's machine, described in the repository's own description as a work in progress, so treat it as a reference rather than as a product. That the release tags are named rather than numbered, so there is no version to pin and no changelog to read, and the tags tell you nothing about compatibility. And that the setup block is copied by hand and contains at least one mistake: the editor plugin is cloned into a path that does not exist yet, so following it verbatim creates a stray directory. The licence is a public domain dedication, which makes reuse easier than most dotfile repositories allow.
Frequently asked questions
What is the xero dotfiles repository?
A personal Linux configuration managed with GNU Stow, covering the interactive shell, a terminal emulator, a multiplexer, an editor, version control, signing keys, secure shell, some helper scripts and a server setup script. It is dedicated to the public domain, and the repository describes itself as a perpetual work in progress rather than a released tool.
How do I install the xero dotfiles?
Clone the repository, change into it, and run Stow with the folders you want and a target of your home directory, for example `stow zsh -t ~` for the shell files or `stow fun -t /usr/local/` for the helper scripts. Uninstalling is `stow -D zsh`. A one-shot alternative is the setup script at the root of the repository, which does the clone, the linking and the third-party plugin installs together.
What is the Stow gotcha in the xero dotfiles readme?
Stow can only create a symlink if the destination file does not already exist, so any default configuration file a program wrote when it was installed has to be deleted first before you can link your own. The readme notes this applies to files only and not to directories, and links an issue in the repository for further notes.
Does xero dotfiles still support tiling window managers?
Not on the default branch. The window manager configurations, two of which are named in the note, were moved to a separate `classic` branch and are not actively maintained, because the author now works in the terminal. The default branch still carries directories from the earlier graphical setup alongside the terminal ones.
How are the xero dotfiles released?
There is no version numbering. The two visible tags are named with words rather than version numbers, one from March 2025 and one from August 2024, so there is nothing to pin a checkout to and nothing in a tag that indicates what changed. The default branch has been pushed to more recently than either tag.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/xero-dotfiles)Star history chart for your README
[](https://hysenlabs.com/projects/xero-dotfiles)Was this useful?