would obviate the need to implement search operators

You can also add the output from an inbuilt search to a queue. Do a search and click the button at the top of the search pane to try it out. You can also right click on folders, files and links to add them to queues through the context menu.

I'm having trouble using any of these methods of adding notes in bulk to the queue. I can't really find the new button at the top of the search pane. And right clicking on files/folders doesn't show anything related to the plugin? Adding everything to the initial queue would really make it easy to get going with IW!

From: https://help.supermemo.org/wiki/Neural_creativity

Spreading activation algorithm
Neural review will go through the sequence determined by spreading activation. In that activation, concepts have higher priority than links, or knowledge tree. However, knowledge tree will be participating as well (with lower weights). Activation will spread slowly to unrelated sibling articles whose relative priorities will increase in absence of children, concept links, and the like. In other words, only small collections will make neural review pointless. Concept maps are not obligatory.

Priorities are combined to determine the spread of activation:

associated concepts are added to the queue at CombinedPriority(Priority,0.01)
links are added at CombinedPriority(Priority,0.05)
descendants at CombinedPriority(Priority,0.16)
siblings at CombinedPriority(Priority,0.26) (or up to 0.5 for unrelated siblings containing full articles)
The procedure is repeated recursively with successive layers taking random picks from the queue such that a pick is more likely for a higher priority

function CombinePriority(OriginalP,GroupP:real):real;
//e.g. element of P=0.2 for a group of P=0.6 should yield (1-0.2)(1-0.6)=0.32
var OP,GP:real;
begin
OP:=1-OriginalP;
GP:=1-GroupP;
Result:=1-OP*GP;
end;
This is the status for Feb 26, 2016. The sequence, priorities, and other parameters will change in the future. It all depends on user feedback and field tests.

Upon installing the plugin, I configured it to use a queue file of "To Review" under my "Inbox" folder, then tried to open the queue file. Nothing happened, so I checked the console and saw "Error: Folder already exists". Apparently the default queue creation unconditionally tries to create a folder, rather than verifying whether the folder exists first.

(It's also not clear to me why there are separate settings for the file and folder names in the first place, vs. using a single note specifier field (with suggestions) as is done by the Zettelkasten prefixer, daily notes, and other plugins' settings for template files.)

Hi! This plugin is amazing, thank you a lot for the effort you put in.

Would it be possible to automatically remove deleted notes from the queue? Otherwise the plugin creates empty notes with the header once they come up in the queue.

Add the ability to bulk add by folder first, then tags and other identifiers.

• Refactor a little bit
• Error checking, handling and logging

From Zander: Just show a subset every day depending on when you last saw them

• whether the active note is in your queue
• show the priority
• show notes
• ability to change priority of the current repetition

"For each linked note in the current note, find the notes / blocks that are linked to from the current note. If any are part of my incremental writing queue, show them to me in order of priority"

Great plugin. Really useful.
So far only issue for me is I can't use it on mobile.
Happy to test it out on mobile if you would like.

• Scheduler: Simple or AFactor
• A Factor
• Default interval

It would be nice to be able to check this option and stick to the defaults.

I really like the concept of inbox processing from Andy Matuschak and it seems like this plugin could support it with a few tweaks. Would it be possible to add options when marking a repetition complete to adjust the interval time like shown in this video: https://www.youtube.com/watch?v=zG5r7QIY_TM (where you can set it to normal repetition time, sooner, or later)

Perhaps you can do something like the Spaced Repetition plugin that uses user-defined tag(s) to indicate which notes are added the the queue.

This would be preferable to adding every note manually to the queue and having every note added the the queue.

Originally posted by @krisbalintona in #15 (comment)

Huge thanks to @pjeby for these suggestions:

FYI, there are some problems with your versioning. manifest.json is missing the version number, and your version tags must not start with a 'v'. Also, you have an unused private function ellipsis. But the concept of the plugin is intriguing and I'll want to give it a try some time.

Oh, also, you don't need to put (IW) at the end of all your command names because they'll be listed in the command palette as "Obsidian Incremental Writing Plugin: Next repetition"

Which incidentally, there is no reason to include the words "Obsidian" or "Plugin" in the name field of your manifest, as they will be redundant when displayed in Obsidian's list of plugins. 😉

So calling it just "Incremental Writing" would suffice and result in command names like "Incremental Writing: Next repetition"

The idea of using a markdown table as a (link-preserving) database was very clever, though. I'm curious how it handles names or text with | in, as I didn't look at how parsing or rendering are done yet.

The idea of using a markdown table as a (link-preserving) database was very clever, though. I'm curious how it handles names or text with | in, as I didn't look at how parsing or rendering are done yet.

Be sure to put in a PR to the obsidianmd/obsidian-releases repo to get it included in the official plugin directory once you do. I'm really looking forward to using it, and to some of your planned improvements. Btw, do you have any plan to allow targeting sections, or just blocks and notes?