Underpowered Files

pending

by Oleksandr Porubaimikh

Style files and folders in the file explorer with bold, italic, and strikethrough effects. Supports cascade inheritance.

Updated 2mo ago0BSDDiscovered via Obsidian Unofficial Plugins
View on GitHub

Underpowered Files

Style files and folders in the Obsidian file explorer with bold, italic, and strikethrough effects. Supports cascade inheritance so folder styles can automatically apply to their children.

Features

  • Bold, italic, and strikethrough styling for any file or folder in your vault
  • Cascade inheritance — enable cascade on a folder to automatically apply its styles to all children
  • Override inherited styles — children can override or disable styles inherited from parent folders
  • Context menu integration — right-click any file or folder to quickly toggle styles
  • Automatic path tracking — styles follow files when renamed or moved

Usage

  1. Right-click any file or folder in the file explorer
  2. Select a style (Bold, Italic, or Strikethrough) to toggle it
  3. For folders, optionally enable cascade to apply the style to all contents

Cascade behavior

When cascade is enabled on a folder:

  • All files and subfolders inherit the folder's styles
  • Children can override inherited styles by setting their own
  • Children can explicitly disable an inherited style

Installation

From Obsidian Community Plugins

  1. Open Settings → Community plugins
  2. Select Browse and search for "Underpowered Files"
  3. Select Install, then Enable

Manual installation

  1. Download main.js, manifest.json, and styles.css from the latest release
  2. Create a folder called underpowered-files in your vault's .obsidian/plugins/ directory
  3. Copy the downloaded files into that folder
  4. Reload Obsidian and enable the plugin in Settings → Community plugins

Settings

  • Clear all styles — Remove all styling rules at once

Development

# Install dependencies
npm install

# Build for development (watch mode)
npm run dev

# Build for production
npm run build

# Run linter
npm run lint

License

0-BSD

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.