| Age | Commit message (Expand) | Author |
|---|
| 2024-01-15 | [fix] Fix bug from 5fefd3d for multiple cloze review...- Update note after all clozes have been revealed and add comment as reminder
| Thanos Apollo |
| 2024-01-15 | gnosis-review--algorithm: Use total successful reviews...Previous implementation was using total successful reviews in a row
| Thanos Apollo |
| 2024-01-15 | gnosis-algorithm: Fix for first interval | Thanos Apollo |
| 2024-01-15 | Merge branch '#fix-review-y-or-n' for version 0.1.1...- Fix review of y-or-n type
| Thanos Apollo |
| 2024-01-15 | [fix] gnosis-review-y-or-n...- Remove previous unused user-input keyword
- Fix name typo
| Thanos Apollo |
| 2024-01-14 | Merge branch version '0.1.0' into master...This is marks the first "release" of gnosis, it's still under heavy
development, but the fundamental use is there. More features will be
added in the future, that should not affect notes created using this
version.
0.1.0 | Thanos Apollo |
| 2024-01-14 | gnosis-dev: Add y-or-n type | Thanos Apollo |
| 2024-01-14 | Merge branch '#y-or-n' into testing...Adding note type of y-or-n and fixing issues with with
gnosis-edit-mode
y-or-n type note is one that has an answer value of char y or n.
| Thanos Apollo |
| 2024-01-14 | [fix] Fix gnosis-edit-mode-map...Having gnosis-edit-mode-map defined after gnosis-edit-mode does not
work, it needs to be defined before
| Thanos Apollo |
| 2024-01-14 | Add gnsois-review-y-or-n & update all other funcs for y-or-n type | Thanos Apollo |
| 2024-01-14 | Add gnosis-display-y-or-n-answer...Display answer for note with face depending on the value of success
| Thanos Apollo |
| 2024-01-14 | Add gnosis-add-note--y-or-n & gnosis-add-note-y-or-n...Functions to add note type y-or-n,
gnosis-add-note--y-or-n is the hidden function that interacts with
gnosis-add-note-fields & gnosis-add-note-y-or-n that passes values interactively
| Thanos Apollo |
| 2024-01-14 | gnosis-algorithm-interval: Add cond for when last interval is 0...- This could occur in custom review sessions, option should be added
to have the same for success 0, but I didn't have any issues _yet_,
will revisit this soon
- Update docstrings & add comments for this
- Fix successful-reviews value
| Thanos Apollo |
| 2024-01-14 | gnosis-algorithm-interval: Update docstring | Thanos Apollo |
| 2024-01-14 | gnosis-dev: fix typos | Thanos Apollo |
| 2024-01-14 | Add gnosis-face-next-review & update docstrings for faces | Thanos Apollo |
| 2024-01-14 | [fix] Fix review of cloze type...Fix typos and previously used logic
| Thanos Apollo |
| 2024-01-14 | Add gnosis-display--next-review...Display next review value
| Thanos Apollo |
| 2024-01-14 | Add gnosis-edit-save-exit...Function to exit recursive edit & save changes
- Add gnosis-edit-exit on gnosis-edit-mode-map
| Thanos Apollo |
| 2024-01-11 | Redo gnosis-dev-test | Thanos Apollo |
| 2024-01-10 | gnosis-face-extra: Inherit italic...Use italic face & change foreground value
This way we keep the same face but do not depend on markdown-mode
--Suggested by Protesilaos Stavrou--
| Thanos Apollo |
| 2024-01-10 | gnosis-select & gnosis--insert-into: Update docstrings | Thanos Apollo |
| 2024-01-10 | gnosis-compare-strings: Redo without let statement | Thanos Apollo |
| 2024-01-10 | Redo gnosis-suspend-note...Use cl-defun and add optional value for unsuspend, this function
should also be used to unsuspend notes
| Thanos Apollo |
| 2024-01-10 | gnosis-edit-mode-map: Use exit-recursive-edit instead of throw 'exit | Thanos Apollo |
| 2024-01-10 | Redo README as markdown | Thanos Apollo |
| 2024-01-09 | Merge branch '#fix-review-due-notes' into testing...Redo checking if note is due
- Avoid depending on emacsql
- Seperate checking if it's suspended or not
| Thanos Apollo |
| 2024-01-09 | Rewrite gnosis-review-get-due-notes | Thanos Apollo |
| 2024-01-09 | Add gnosis-review-is-due-today-p | Thanos Apollo |
| 2024-01-09 | Rewrite gnosis-review-is-due-p | Thanos Apollo |
| 2024-01-09 | Add gnosis-past-or-present-p...Seperate the comparing of dates, emacsql is way too buggy for
comparing lists directly
| Thanos Apollo |
| 2024-01-08 | Merge branch '#clean' into testing...- Remove unused progn
- Add todo's
| Thanos Apollo |
| 2024-01-08 | Add todo's & remove unused progn | Thanos Apollo |
| 2024-01-08 | gnosis-review--session: Fix message for no notes...Redo with if statement & update message
| Thanos Apollo |
| 2024-01-06 | Merge branch 'testing': Fix review of specified tags | Thanos Apollo |
| 2024-01-06 | Update gnosis-get-tags--unique...Flatten returned list
| Thanos Apollo |
| 2024-01-04 | Update gnosis-get-tags--unique...Flatten returned list
| Thanos Apollo |
| 2024-01-04 | gnosis-review: Fix review of due notes of specified tags...This should be renamed soon as well...
| Thanos Apollo |
| 2024-01-04 | Redo gnosis-tag-prompt as cl-defun | Thanos Apollo |
| 2024-01-04 | Add gnosis-due-tags | Thanos Apollo |
| 2024-01-04 | gnosis-db: Redo as defconst | Thanos Apollo |
| 2024-01-04 | gnosis-review: Add review session for due notes of deck | Thanos Apollo |
| 2024-01-04 | Add gnosis-define-deck...Function to export deck notes as & import them as DECK
| Thanos Apollo |
| 2024-01-04 | Add gnosis-export-deck..."Export notes for deck in FILENAME."
FILENAME: The name of the file to save the exported deck.
This function prompts the user to provide a deck name and allows the
user to specify a filename for exporting notes belonging to that deck.
It then retrieves all the notes associated with the deck and exports
them.
The exported notes are formatted as an Emacs Lisp code block that can
be evaluated to recreate the deck with its associated notes. The
resulting code is saved to a file with the provided FILENAME and a
'.el' extension is added automatically.
Each note is exported using the `gnosis-export-note` function. The
generated code includes a call to `gnosis-define-deck` with the deck
name and all notes formatted as nested lists
| Thanos Apollo |
| 2024-01-04 | Add dd gnosis-export-note..."Export fields for note with value of id ID."
ID: Identifier of the note to export.
This function retrieves the fields of a note with the given ID and
inserts them into the current buffer. Each field is represented as a
property list entry. The following fields are exported: type, main,
options, answer, tags, extra-notes, image, and second-image.
The exported fields are formatted as key-value pairs with a colon,
e.g., :field value. The fields are inserted sequentially into the
buffer. For certain field values, like lists or nil, special
formatting is applied.
If the value is a list, the elements are formatted as strings and
enclosed in double quotes.
If the value is nil, the field is exported as :field nil.
All other values are treated as strings and exported with double
quotes.
The final exported note is indented using the `indent-region' function
| Thanos Apollo |
| 2024-01-04 | Add gnosis-get-notes-for-deck...Return a list of ID vlaues for each note with value of deck-id DECK
| Thanos Apollo |
| 2024-01-04 | gnosis-add-note-fields: Add condition-case & update docstring | Thanos Apollo |
| 2024-01-04 | Remove gnosis-faces.el & notes.el...Add faces on gnosis.el
| Thanos Apollo |
| 2024-01-04 | Add gnosis-edit-mode & map...gnosis-edit-mode, a mode derived from emacs-lisp with that has keybind
C-c C-c to a #'lambda that evaluates & kills buffer, exiting
recursive-edit loop
| Thanos Apollo |
| 2024-01-04 | Add gnosis-get-deck-due-notes...Get due notes of specified deck-id
| Thanos Apollo |
