Metalayer
When you install this package, you will get a command line tool called metalayer.
To initialize your knowledge repo, run the following command, which will walk you through the process:
metalayer init
When you've initialized the knowledge repo, run the following command:
metalayer run
This will start recording your screen(s) and printing a bunch of stuff. Once you start looking at stuff related to the folders you created, files should start appearing in those folders. After a few minutes, open up your Knowledge Repo folder up in Obsidian to explore the notes!
To stop the metalayer. Type q + enter in the terminal window where you ran metalayer run.
This stops the program gracefully, but if you need to hard-stop just type ^C (control + c).
Manual Set-up (Optional)
This section is OPTIONAL. Ignore unless you want/need to set up the metalayer manually.
Permissions
For each of the following pages in the settings app, you need to check the box next to Terminal or add Terminal.
- System Preferences > Privacy & Security > Screen Recording
- System Preferences > Privacy & Security > Accessibility
- System Preferences > Privacy & Security > Input Monitoring
If you're using chrome, you also need to enable apple events since metalayer uses those to get the title of the active tab and other metadata. To do this, open chrome then click View > Developer > Allow JavaScript from Apple Events.
Setting up your knowledge repo
The tutorial in metalayer init will walk you through this, but in case you want to do it yourself this heres how:
Before you start recording your screen and saving auto-generated markdown notes to a folder, you need to first create the folder. I call mine Knowledge Repo. To set your folder as the obsidian vault root, run:
metalayer set-vault-dir <path-to-your-folder>
Then, create a subfolder for each topic you want to record notes for.
NOTE: for each subfolder, you need to create a file called _desciption.md,
which should have a 1-3 sentence description of what you want to be indexed into that folder.
A more specific description will make filtering quality better. Here's an example from my repo:
Knowledge Repo
├── Control Theory
│ ├── _description.md
│ └── Model Predictive Control
│ └── _description.md
└── Evolutionary Algorithms
└── _description.md
Evolutionary Algorithms/_description.md:
Everything related to evolultionary algorithms an genetic algorithms, including motiviation,
parallels to biological evolution, computational properties, implementation, variants, applications, etc.
Metadata
Release files for auto-obsidian 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| auto-obsidian-0.1.3.tar.gz | 28.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_obsidian-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.0 kB
Release files / auto-obsidian-0.1.3.tar.gz
| Download URL | auto-obsidian-0.1.3.tar.gz |
|---|---|
| Size | 28.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4072827ff59e2b54d5523442c4256bf462ac9e20ac05d17a1d74483f34dacc68
|
|
BLAKE2b-256 checksum How to use checksums |
3885530316cd0f53e069e8b9ddf7bca1decd9c6c95822872ab49ddaa7a9a7c6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.13
|
Release files / auto_obsidian-0.1.3-py3-none-any.whl
| Download URL | auto_obsidian-0.1.3-py3-none-any.whl |
|---|---|
| Size | 38.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0d00fed33752a1aec74d2902d32f18b4e546fb58cd79baefe1dae77f9689fdb
|
|
BLAKE2b-256 checksum How to use checksums |
c7acbada39c88ded628da582332ee9262d117122daa634f330e0f6aae2899a2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.13
|