Perilous Writing
approvedby Sameer Ismail
Write continuously—or lose all progress.
Perilous Writing
An Obsidian plugin which demands writing output, at the threat of bludgeoning your in-progress work. Emulates Manu Ebert's excellent The Most Dangerous Writing App.
[☨] (Experimental—bug reports welcome.)
Usage
Warning: If a session is not completed successfully then your in-session work will be irrevocably deleted. Caveat emptor.
-
Install the plugin. See below.
-
Open the command palette and choose either a short session (default of five minutes), a long session (default of ten minutes), or a custom-length session. (The respective default durations can be changed in the settings tab.)
-
A light gray bar will appear at the top of the editor. It represents the session's progress. The session will begin after the next keypress.
-
Begin writing. If you stop writing for five seconds your in-session additions will be deleted. You'll be warned after two seconds of inactivity.
-
Only new characters reset the timer—backspace does not. Neither do normal-mode operations under Vim emulation. On completion of a successful session, progress is preserved.
-
Remove the progress bar with the “Clear session” command.
Installation
Community Plugins
Search for “Perilous Writing” in the community plugins tab.
Manual
Download the latest release, and copy the main.js, styles.css, and manifest.json files into a new plugin directory, like (4) and (5) below.
From source
-
Clone the repository.
-
Install the dependencies. Through
yarnornpm installin the directory root. -
Build the plugin with
yarn buildornpm run build. This will produce amain.jsfile. -
Create a directory for the plugin in your vault's directory.
mkdir -p $VAULT_SOURCE/.obsidian/plugins/perilous-writing -
Copy the
main.js,styles.css, andmanifest.jsonfiles into that directory.cp main.js styles.css manifest.json $VAULT_SOURCE/.obsidian/perilous-writing -
Enable the plugin in Obsidian's settings tab.
Acknowledgements
Inspired by Manu Ebert's The Most Dangerous Writing App.
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.