| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Return total deck note count in a list. Will be used to output decks.
|
|
- Specify tabulated-list-format
- Fix bug, when a note was deleted it would have broken the dashboard
- Specify keybindings using local-set-key
|
|
Use multipel choice to select how to create dashboard, for now the
options are only for notes & decks. Future versions should filter for
tags etc
|
|
|
|
Edit contents of a deck with a given ID. This function is meant to be
used from within a *gnosis-dashboard* buffer. Uses custom kbd via
local-set-key, since gnosis-dashboard mode is also used by
gnosis-edit-notes, this is viable alternative, if you have any other
recommendations feel free to email them to me
|
|
- Use gnosis-assert funcs to make error messages descreptive
- Use cl-loop to simplify gnosis-update
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If id is given, return the name for deck id
|
|
|
|
Add failure-factor, ef-increase, ef-decrease, ef-threshold for decks
table. These values will be applied to all notes for deck.
|
|
We will be specified using one of the dashboard create funcs. Value
will be different depending on how the dashboard will be created.
|
|
We will be setting keybindings for editing/suspending locally
depending on how the dashboard has been created, for notes or decks etc
|
|
Add function as argument to be used as exit func. This will make it
easier to reuse with other funcs
|
|
- Rename frequency->threshold
- Update module desc
|
|
- Make sure correct value types are given
|
|
Deprecated
|
|
|
|
If c-successes/c-failures is 0 change-p would return t, triggering the
update frequency. Using max 1 would fixes this.
|
|
Calculate new ef using gnosis-algorithm
|
|
Use gnosis-algorithm-next-ef & gnosis-algorithm-next-interval. Return
them as list for simplicity
|
|
Just calculate next interval, previous implementation was out of scope
|
|
Seperate calculation of easiness factor. This will make it easier to
apply changes to increase/decrease value depending on the number of
successful & failed reviews
|
|
|
|
|
|
Frequency by which to update ef increase & decrease values
|
|
Value to decrease ef-decrease by in set frequency
|
|
Value to increase ef-increase value in set frequency
|
|
I'm not a double spacer nor have strong opinions on the subject. But
since most of emacs community prefers this style, I don't mind using it.
|
|
Instead of using gnosis-display-image 'extra-image on every review
note type, just add it to extras. Future refactoring is needed to
simplify gnosis-review-TYPEs
|
|
Use gnosis-get, avoid extra complexity
|
|
|
|
|
|
gnosis-add-note-TYPE now has a :images keyword instead of just an
image, that using gnosis-select-images will return a cons of.
gnosis-add-note--TYPE handles the car & cadr of :images cons as (image
. second-image)
Update docstrings as well.
|
|
If cloze given is not valid throw an error. Just having search-forward
return error alone is confusing.
|
|
Put the value of the example/guide in a variable, this way it will be
easier for experienced users to set it to nil if they find it annoying.
|
|
Having "" tag should be avoided.
|
|
read-from-minibuffer does the same thing, but since not many package
authors use it I thought to avoid it as well, plus we have to make
sure the value will be a string.
|
|
Refactor gnsois-select-images to prompt to select for extra-image as
well, returns a cons (image . second-images).
This way we won't have to recreate a needless function like
gnosis-select-second-image.
|
|
When creating gnosis-edit buffer for NOTE, we have to make sure the
fields will not be deleted accidently be the user and the value of id
won't change.
Use gnosis-edit-read-only-values in gnosis-edit-note.
|
|
After using read-only values, we can't clear the buffer. We have to
kill it and then recreate it for each time we call gnosis-edit-note
|
|
Explain the reason behind the naming conventions used
|
