by Vishwas Upponi
Automatically opens specified notes in Reading View while letting you choose your preferred default view mode for all other notes.
↓ 27 downloadsUpdated 11d agoMIT
Auto Reading View
An Obsidian plugin that automatically opens specified notes in Reading View, while giving you full control over the default view mode for all other notes in your vault.
✨ Features
- Targeted Reading View: Specify notes (like Dashboards, Homepages, MOCs, or reference notes) to automatically open in Reading View upon opening.
- Configurable Mode for Other Notes: Choose how all other non-targeted notes in your vault should open:
- Live Preview (Default)
- Source Mode (Raw Markdown)
- Do Not Change (Keeps whatever mode the current tab was already in)
- Interactive Note Autocompletion: Easily search and add notes from your vault directly within the plugin settings with instant autocompletion.
- Editing Freedom: Opening a target page sets Reading View once on file open—you can switch to Edit mode (
Ctrl + E) at any time without the plugin fighting or overriding you while you type.
🚀 Installation
Manual Installation
- Download the latest release (
main.jsandmanifest.json). - Inside your Obsidian vault, navigate to
.obsidian/plugins/. - Create a folder named
auto-reading-viewand placemain.jsandmanifest.jsoninside it. - In Obsidian, go to Settings → Community plugins, click Reload plugins, and enable Auto Reading View.
⚙️ Settings
- Mode for Other Pages:
- Live Preview (Default): Ensures standard notes open in Live Preview editing mode.
- Source Mode: Opens other notes in raw markdown source mode.
- Do Not Change: Leaves the active tab mode untouched.
- Target Pages:
- Search and add specific note names or paths that should open in Reading View.
📄 License
This project is licensed under the MIT License.
Developed by Vishwas Upponi.
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.