| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
- Use gnosis-dashboard-note-ids
|
|
|
|
- Adjust for notes with "\n"
- Use format, prin1-to-string displays notes quotes ("")
- Remove display-line-numbers-mode, this should be configured by the
user.
|
|
- Query database for note & display notes that match query on
dashboard
|
|
|
|
- Major changes on dashboard
- Redo how note-ids are collected
- Add support for tags
- Rewrite how gnosis-review-TYPE works, now these funcs need to return
the review result, either t for success or nil for failure.
- Add override
- Override review result, e.g change review result from failure to
success
- Minor bug fixes on image display
|
|
|
|
- gnosis-dashboard-output-decks & notes functions are the ones that
should pop to a new buffer.
- gnosis-dashboard should only handle note-id collection
|
|
Reverses the result of review
|
|
|
|
- Review functions return a boolean value for success.
This way it can be overriden.
|
|
Since we will be displaying next date before we use
gnosis-review--update, we will have to calculate the next date before
we update note value in db.
|
|
- Override review result
- gnosis-review--update will be used only on gnosis-review--sesion.
- gnosis-review-TYPE functions should return t or nil, for
success or failure of review.
|
|
|
|
- Use lowercase
- Prompt for gnosis-dashboard-type before switching to buffer
|
