| Age | Commit message (Collapse) | Author |
|---|
|
Returning 0 would break algorithm implementation
|
|
|
|
|
|
|
|
Returning 0 would break algorithm implementation
|
|
|
|
|
|
|
|
Call gnosis-completing-read-function, disable history input, shuffle
seq order.
This should make it easier to add new gnosis types
|
|
Call gnosis-completing-read-function, disable history input, shuffle
seq order.
This should make it easier to add new gnosis types
|
|
|
|
This version brings fixes for gnosis algorithm:
Fix algorithm ff, give priority to deck ff over note's ff.
Fix gnosis-vc-pull, by changing gnosis-db to defvar we can now update
the value when we pull changes.
Until the first 2 successful reviews, the next interval upon failure
will be 0, meaning it will be reviewed the same day.
Adjust success next interval to not be surpassed by failure, this
would occur if user hadn't reviewed an item/used gnosis in a long time.
|
|
|
|
If last-interval is 0, use 1 instead. 0 value could possible occur
with customized initial interval values.
Until 2 successful, have next interval be 0 (review on the same day)
upon failure to recall
|
|
We are updating gnosis-due-notes-total upon calling gnosis-review
|
|
Defconst would not allow the value to change when using gnosis-vc-pull
|
|
|
|
Return the diff between date2, optional arg with default current date.
|
|
Use gnosis-get-note-ff & gnosis-review-last-interval
Previous implementation would not respect note's ff or deck's ff
|
|
|
|
|
|
|
|
|
|
Adjust so that failure-interval is never higher than success-interval,
such us in cases where initial-interval is used
|
|
Improve review interactions/actions
Minor style changes
|
|
|
|
|
|
- Rename to gnosis-review-session
- Use catch-throw to break out of the cl-loop
|
|
Seperate actions to take during review of gnosis note.
Use recursion to be able to do more than one action, e.g edit &
then override note.
|
|
This should be done more elegantly within a gnosis-review-actions
without a y-or-n prompt
|
|
|
|
Previous implementation would not update note value for success upon review
|
|
- Redo note ids as random integer values
- Add feature, view notes of deck in dashboard
- Add delete functions
- Fix modeline performance issues
- Fix deprecated use of suspend
- Refactor adding notes prompts
|
|
|
|
|
|
|
|
Update value of gnosis-due-notes-total during review session
This way user was a count of total due notes during review.
|
|
Make var name clear that it represents total count. due notes might
be asumed as a list of note ids
|
|
|
|
Calling (length (gnosis-review-get-due-notes)) causes performance
issues, especially on old hardware, we store the value on a variable
and update it every 5 minutes or when we finish a review session.
|
|
- Process input given from gnosis-mcq-prompt
|
|
- Use recursion when incorrect formatting is used
- Separate the process of input to a different function
|
|
|
|
|
|
- Remove while statements from gnosis-add-note-TYPE funcs
- Every gnosis-add-note-TYPE must receive `deck` as arg
- gnosis-add-note implements recursion, with deck & type as optional
arguments.
This is done to simplify the logic & improve UI
|
|
- Previous implementation would break the generation of ids after
deleting a note
- Using gnosis-generate-id fixed the previous issue these functions had
|
|
- Generate a unique note id
|
|
|
|
- Use gnosis-tag-prompt to select tags
- Implement 'due' logic on gnosis-select-by-tag
|
|
- From gnosis-dashboard of decks, press RET to view all notes of deck
|
