Add colored relationship lines to your files and folders in Obsidian, based on their nesting level. Enable focus mode to highlight active files and their parent folders, and set the relationship lines to be solid, dotted, or dashed.
- Set the colors to relationship lines
- Show the relationshi 8F07 p lines in the editor
- Focus Mode: Folders and files that are not open are dimmed, including the icon in present.
- Set the relation lines to be solid, dotted or dashed.
Focus mode highlights active files and their parent folders, dimming the rest. In the screenshot above I have two files open, other files and folders are dimmed.
- Open Obsidian Settings
- Navigate to Community Plugins and disable Safe Mode
- Click Browse and search for "Rainbow Tree"
- Install the plugin
- Enable the plugin in your Community Plugins list
In the plugin settings, you can:
- Set the color of the relationship lines for 1-5 levels of nesting
- Enable focus mode that highlights active files and their parent folders, dimming the rest
- Set the relationship lines to be solid, dotted, or dashed
If you encounter any issues or have suggestions:
- Create an issue on GitHub
- Support the development:
Want to contribute or modify the plugin? Here's how to get started with the source code:
-
Create a directory for your GitHub projects:
cd path/to/somewhere mkdir Github cd Github
-
Clone the repository:
git clone https://github.com/bwya77/rainbow-tree.git
-
Navigate to the plugin directory:
cd dynamic-editor-width
-
Install dependencies:
npm install
-
Start development build mode:
npm run dev
This command will keep running in the terminal and automatically rebuild the plugin whenever you make changes to the source code.
-
You'll see a
main.js
file appear in the plugin directory - this is the compiled version of your plugin.
To test your modifications:
- Create a symbolic link or copy your plugin folder to your vault's
.obsidian/plugins/
directory - Enable the plugin in Obsidian's community plugins settings
- Use the developer console (Ctrl+Shift+I) to check for errors and debug
- Fork the repository
- Create a new branch for your feature
- Make your changes
- Submit a pull request with a clear description of your changes