Using ZKM for learning about a software

rwrobinson

Hey!

I'm starting a new job, and I have to learn some new software. I want to put what I learn into my Archive.

I don't know why, but it feels awkward to me to go through the software's documentation and start writing notes about the different features. Intuitively it seems at odds with ZKM. But, I'm don't think it actually is.

But, is that how you'd do it also?

Start with a structure note, and start to branch off into these different features within the software, writing notes about the different features?

Thanks for you thoughts in advance!

ctietze

I'm documenting my journey through what is probably the simplest yet most powerful/annoying/lovable piece of software, Emacs. So yes, I can say it helps

Here's my first one for reference:

# 201803231421 Emacs configuration paths
#emacs #configuration

Global Emacs configuration is located here:

    ~/.emacs.d/init.el

Open it in an Emacs buffer with `C-x C-f`.

• I didn't know how to open files in Emacs, so I put the shortcut at the bottom
• I didn't think I'd remember where this file is placed, because it's in such an awkward location (for an app on a Mac)

Or manipulate what I see on screen, my 2nd note, because I couldn't remember for the life of me how to remove all these window splits, gah!

# 201803231425 Emacs split pane mode shortcuts
#emacs

- `C-x b`: List all buffers
- `C-x 2`: Split vertically
- `C-x 3`: Split horizontally
- `C-x 0`: close this split pane
- `C-x 1`: close all other split panes (single pane mode)
- `C-x o`: Switch to other pane (cycle through)

Note the very bad tagging ;(

Another example: DaVinci Resolve! I'm not a video editor so the industry standards don't mean anything to me.

# 202108242100 DaVinci Resolve Shortcuts to edit
#davinci #shortcuts

- https://motionarray.com/learn/davinci-resolve/davinci-resolve-keyboard-shortcuts/

## Playback control

Works in all modes:

| Key           | Function                            |
| ------------- | ----------------------------------- |
| J / K / L     | ⏪ ⏸ ⏩ (reverse) playback, "shuttle" |
| ⇧ + J / ⇧ + L | fast (reverse) playback             |
| ← / →         | move by frame                       |
| ⌥ + /         | play from in marker to out marker   |

## Marking positions

Marking positions to have convenient jump points without cuts:

| Key   | Function              |
| ----- | --------------------- |
| I     | mark in               |
| ⌥ + I | clear in              |
| O     | mark out              |
| ⌥ + O | clear out             |
| M     | add marker            |
| ⌘ + M | add and modify marker |
| ⇧ + M | modify marker         |
| ⌥ + M | delete marker         |

## Cutting

| Key   | Function                                    |
| ----- | ------------------------------------------- |
| ⌥ + \ | join clips                                  |
| ⌘ + \ | split clips at position                     |
| ⌘ + B | split selected clip (razor)                 |
| Y     | select clips at and after current in track  |
| ⌘ + Y | select clips at and before current in track |

## Editing shortcuts

Don't work in the "cut" mode, but in the "edit" mode

You see these are all very isolated notes. There's no link to be seen. That is, I believe, because I had to start with something. Eventually, structure notes emerged about navigating around in Emacs, about file manipulation, etc., and then these atomic notes above were used there. So they're not orphans anymore

rwrobinson

Very helpful feedback.

Thank you!