hascard: A TUI for reviewing notes using 'flashcards' written with markdown-like syntax.

[ application, bsd3, library, program ] [ Propose Tags ]

Hascard is a text-based user interface for reviewing notes using flashcards. Cards are written in markdown-like syntax. Please see the README file on GitHub at https://github.com/Yvee1/hascard#readme for more information.

[Skip to Readme]
Versions [faq],,,,,,,,
Change log ChangeLog.md
Dependencies base (>=4.7 && <5), brick (>=0.52.1 && <0.56), containers (>0.6.0 && <0.7), directory (>=1.3.3 && <1.4), filepath (>=1.4.2 && <1.5), hascard, megaparsec (>=8.0.0 && <8.1), microlens (>=0.4.11 && <0.5), microlens-platform (>=0.4.1 && <0.5), mwc-random (==0.14.*), optparse-applicative (>=0.15.1 && <0.16), ordered-containers (>=0.2.2 && <0.3), process (>=1.6.5 && <1.7), random-fu (>=0.2.7 && <0.3), strict (>=0.3.2 && <0.4), text (>=1.2.3 && <1.3), vector (>=0.12.0 && <0.13), vty (>=5.28.2 && <5.31), word-wrap (>=0.4.1 && <0.5) [details]
License BSD-3-Clause
Copyright 2020 Steven van den Broek
Author Steven van den Broek
Maintainer stevenvdb@live.nl
Category Application
Home page https://github.com/Yvee1/hascard#readme
Bug tracker https://github.com/Yvee1/hascard/issues
Source repo head: git clone https://github.com/Yvee1/hascard
Uploaded by Yvee1 at 2020-08-20T20:58:26Z
Distributions NixOS:
Executables hascard
Downloads 690 total (128 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2020-08-20 [all 1 reports]


[Index] [Quick Jump]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for hascard-

[back to package description]


Build Status GitHub tag AUR Hackage

A minimal commandline utility for reviewing notes. 'Flashcards' can be written in markdown-like syntax.

<p align="center"> <img alt="a recording of example usage of the hascard application" src="./recordings/recording.gif"> </p>



Installation on Windows is not possible sadly, aside from WSL. This is because hascard depends on vty which only supports unix operating systems (this includes macOS).

Homebrew (for macOS)

For macOS users an installation using homebrew is provided via a custom tap. You can run

brew update
brew install Yvee1/tools/hascard


Ubuntu and macOS binaries are available under releases. To be able to run it from any directory, it has to be added to the PATH. This can be done by copying it to e.g. the /usr/local/bin directory.

Arch Linux

Thanks to loki7990, hascard is also on the AUR: https://aur.archlinux.org/packages/hascard/.


Hascard is also on snapcraft. Installation instructions are on that site. If you already have snap installed you can just install hascard via sudo snap install hascard. By default snap applications are isolated from the system and run in a sandbox. This means that hascard does not have permission to read or write any files on the system aside from those under %HOME/snap/hascard. To be able to read cards also in other directories under the home directory, hascard makes use of the home interface which might need to be enabled manually using sudo snap connect hascard:home :home.

Note: The installation with snapcraft does not work with all terminals, known issues are with alacritty and st, because of problems with terminfo that I do not know how to solve. With me, this did not happen with the other installation methods so try those if you have a somewhat non-standard terminal. If anyone knows what the problem might be, let me know!

Install from source

Another option is to build hascard and install it from source. For this you can use the Haskell build tool called stack, or nix. Then for example clone this repository somewhere:

git clone https://github.com/Yvee1/hascard.git
cd hascard

and do stack install hascard or nix-build respectively.


Simply run hascard to open the main application. Menu navigation can be done with the arrow keys or with the 'j' and 'k' keys. The controls for the different cards can be found at the bottom of the screen by default. This, and a couple other things, can be changed in the settings menu. A deck of cards can be opened using the built-in filebrowser, and recently selected decks will appear in the selection menu. The application can also be run directly on a file by giving it as an argument. These decks of flashcards are written in plain text, this is explained in section Cards.

After finishing a deck, there is an option to create new decks from the correctly answered or incorrectly answered cards, or both. The correct cards of a file named deck.txt are stored in deck+.txt in the same folder, and the incorrect ones in the file deck-.txt. Make sure you do not have files of those names that you want to keep since these will be overwritten.


The CLI provides some options for running hascard; the most interesting are:

  -a,--amount n            Use the first n cards in the deck (most useful
                           combined with shuffle)
  -c,--chunk i/n           Split the deck into n chunks, and review the i'th
                           one. Counting starts at 1.
  -s,--shuffle             Randomize card order
As an example, say you have a file `deck.txt` with lots of cards in it and you want to review 5 random ones, you can use `hascard deck -s -a 5`. Here `-s` shuffles the deck and `-a 5` specifies we only want to look at 5 of them.

## Cards
Decks of cards are written in `.txt` or `.md` files. Cards are seperated with a line containing three dashes `---`. For examples, see the [`/cards`](https://github.com/Yvee1/hascard/tree/master/cards) directory. In this section the 5 different types of cards are listed, with the syntax and how it is represented in the application.

### Definition
This is the simplest card, it simply has a title and can be flipped to show the contents. For example the following card

Word or question

Explanation or definition of this word, or the answer to the question.

will result in
<p align="center">
  <img src="./recordings/definition.gif"></img>

### Multiple choice
This is a typical multiple choice question. The question starts with a `#` and the choices follow. Only one answer is correct, and is indicated by a `*`, the other questions are preceded by a `-`. As an example, the following text

Multiple choice question, (only one answer is right)

  • Choice 1
  • Choice 2 (this is the correct answer)
  • Choice 3
  • Choice 4

gets rendered as
<p align="center">
  <img src="./recordings/multiple-choice.gif"></img>

### Multiple answer
Multiple choice questions with multiple possible answers is also possible. Here again the question starts with `#` and the options follow. Preceding each option is a box `[ ]` that is filled with a `*` or a `x` if it is correct. For example

Multiple answer question

[*] Option 1 (this is a correct answer) [ ] Option 2 [*] Option 3 (this is a correct answer) [ ] Option 4

results in
<p align="center">
  <img src="./recordings/multiple-answer.gif"></img>

### Open question
Open questions are also supported. The words that have to be filled in should be surrounded by underscores `_`. Underscores can also be escaped by `\_` if they are part of the text, like is done in [`cards/analysis3.txt`](https://github.com/Yvee1/hascard/blob/48b5c0751ac72df791402b88c033e05488c9350d/cards/analysis3.txt#L34-L37t). Multiple answer possibilities can also be given by seperating them with vertical bars `|`. As an example, the card

Fill in the gaps

The symbol € is for the currency named Euro, and is used in the EU|European Union.

behaves like this

<p align="center">
  <img src="./recordings/gapped-question.gif"></img>

### Reorder question
This is a question where you have to put the elements in the correct order. Each element is preceded by a number indicating their correct place. The elements are rendered in the same order as they are written. For example the card

Order the letters in alphabetical order

  1. u
  2. l
  3. p
  4. s
will look like
<p align="center">
  <img src="./recordings/reordering.gif"></img>

## Miscellaneous info
Written in Haskell, UI built with [brick](https://github.com/jtdaugherty/brick) and parsing of cards done with [parsec](https://github.com/haskell/parsec). Recordings of the terminal were made using [terminalizer](https://github.com/faressoft/terminalizer). The filebrowser widget was mostly copied from the brick [filebrowser demo program](https://github.com/jtdaugherty/brick/blob/master/programs/FileBrowserDemo.hs). Homebrew and Travis configurations were made much easier by [the tutorial from Chris Penner](https://chrispenner.ca/posts/homebrew-haskell).