Hi Typora team,
I would like to request a feature enhancement regarding the File Tree sidebar behavior.
Currently, folders that are marked as hidden — especially dot-folders such as .kiro, .config, .docs, .assets, or other project-related hidden directories — do not appear in the File Tree view. This behavior makes it difficult to work on projects where documentation or assets are intentionally stored inside hidden folders for organizational or structural reasons.
What I am requesting
Please consider adding an option (in Preferences or advanced settings) that allows users to:
- Show hidden folders (e.g., dot-folders) in the File Tree,
- Or toggle visibility on/off depending on each user's workflow.
Why this is useful
- Many development/project structures rely on dot-folders for configuration or metadata.
- Some teams place Markdown documentation inside hidden directories to avoid exposing them in build pipelines.
- Having the ability to display or hide these folders would greatly improve Typora’s usability for technical documentation workflows.
Environment
- Typora version: (1.12.4)
- OS: (Windows/macOS/Linux)
This enhancement would offer more flexibility without affecting users who prefer the current behavior.
Thank you for considering this request, and for your continued work on Typora — it’s an excellent editor.
Best regards,
Hi Typora team,
I would like to request a feature enhancement regarding the File Tree sidebar behavior.
Currently, folders that are marked as hidden — especially dot-folders such as .kiro, .config, .docs, .assets, or other project-related hidden directories — do not appear in the File Tree view. This behavior makes it difficult to work on projects where documentation or assets are intentionally stored inside hidden folders for organizational or structural reasons.
What I am requesting
Please consider adding an option (in Preferences or advanced settings) that allows users to:
Why this is useful
Environment
This enhancement would offer more flexibility without affecting users who prefer the current behavior.
Thank you for considering this request, and for your continued work on Typora — it’s an excellent editor.
Best regards,