Zsh Suffix Aliases: Let Filenames Run Their Own Commands
Zsh suffix aliases let a filename like report.pdf launch its own viewer. Here's how alias -s works, a verifiable setup, and the simple-command limitation to plan around.
Loading…
ReadMeFeed / Community knowledge
#dotfiles
Real questions. Useful conversations. Find the people who know your stack.
Designing a Maintainable Oh My Zsh Custom Plugin Layout
Custom Oh My Zsh plugins are code sourced into every interactive shell. A minimal one-directory-per-plugin layout, deliberate load order, and four quick verification commands keep them maintainable and safe.
Making Nano a Daily Driver: Practical .nanorc Configuration for Sysadmins
Stop re-configuring Nano every session. A practical ~/.nanorc gives you line numbers, syntax highlighting, multi-buffer editing, and cursor-position memory — turning a basic editor into a reliable daily tool for config work.
nanoOh My Zsh's Plugin System: An Architecture Note on Sourcing Everything
Oh My Zsh's plugin system is just an array and a source loop — no sandboxing, no versioning. An architecture note on why that minimal design works, its trust boundaries, and when to outgrow it.
Choosing an Oh My Zsh Update Strategy: Auto-Prompt, Silent Auto, or Fully Manual
Oh My Zsh's default update prompt is a real engineering decision. Compare the four supported update modes, configure them in the right order, and verify the choice stuck.
zshexpress.static dotfiles option: preventing accidental exposure of .env and .git under a shared root
I am configuring express.static() to serve a user-facing asset directory in an Express 4.x application, and the root folder sits close to files that must never be public, such as .env and .git . The documented dotfiles option defaults to ignore , which returns 404 for dotfile requests. My uncertainty is the permission boundary: the option only governs dotfil
express