Plain Text Supremacy With Emacs: git-link, file-backed buffers, repo, daemons, auth-sources & pass скачать в хорошем качестве

Plain Text Supremacy With Emacs: git-link, file-backed buffers, repo, daemons, auth-sources & pass

NOTE: Use the video chapters (lol), This video contains many tangents (and no audio), so watching it from beginning to end is likely insufferable. Instead, click a video chapter: one that interests you or choose one at random. An hour of a day in the life of an Emacs user with ADHD. 0:00 posting a tweet with a screenshot and `M-x git-link` 0:30 accidentally sending emacs to background with `C-z` 2:00 using `M-x git-link` without a file-backed buffer 2:30 checking for warnings & errors in the messages buffer with `F1 e` 3:20 using `M-x git-link` in a file-backed buffer 5:00 counting the 1,822 repositories I cloned with Google's repo tool 6:10 using repo to keep updated copies of Guix channels for reference 10:00 attempting to send notification using `M-: (notifications-notify "string")` 10:45 attempting with `M-! notify-send "string"` but OBS has cut off my notifications 12:00 browsing systemd units with daemons.el 13:00 checking daemons.el source for references to display a tree view 13:40 using `M-s r` to scan daemons.el source with `counsel-ripgrep` 15:20 discoverying that daemons.el uses git worktrees for automation 16:00 saving minibuffer completion results with embark-collect 17:00 using `org-roam-dailies-goto-today` to save worktree refs for later 19:20 expanding an org example block with yasnippet 20:10 changing the mode of the example block to grep-mode 21:00 getting the grep-mode links in search result to work 21:30 clarifying how to use `embark-collect` from almost any minibuffer 22:40 finding references to other embark keybindings in its sourcecode 24:00 demonstrating the difference between an `org-src` buffer and a `grep-mode` buffer 28:40 grep-mode links should fail, but refcard-ERT project uses the same script 30:00 using `tree` to show the `git worktree` i used for the Make Roanoke website 30:50 using `insert-char` to find & replace non-breaking spaces 31:50 dumping the `git config` for worktree layout that uses a bare checkout 33:30 more clearly showing the filetree for `git worktree` 34:20 dumping the ".git" directories for each `git worktree` 35:00 showing the `git-link` function's "interactive" specification 36:40 showing the Repo XML for the Blender Project's repositories 38:45 ob-restclient block to pull all Blender projects via their Gitlab API 39:00 how ob-restclient pulls a gpg-encrypted API token with "auth-sources" 40:00 A ".password-store" directory tree that lets "forge.el" and "ghub.el" use `unix pass` 41:20 noting that it's a PITA to learn to setup `auth-source-pass-get` without "netrc" format 42:00 noting potential issues with API tokens and logfiles to beware when using org-babel 42:45 comparing Google's `repo` with Github Lists using the `gh` command (latter is not secure) 44:25 radian-software/riju documents Dockerfile for 100+ programming language environments! 45:00 gloss over the Makefile in riju to connect its YAML format to its docker builds 46:40 wondering why you have a job if you can't grok how a local copy of riju's source is valuable 47:00 collapsing the "stack frames" of the 45-minute "tangent stack" ... 47:00 collapsing the "stack frames" of the 45-minute "tangent stack" ... 48:05 opening a tensorflow project that's synced with repo 48:50 showing the org-babel blocks in README.org that generate default.xml for tensorflow 49:30 using `projectil-find-file` to search "tensorflow/models" repo for "*.proto" files 52:05 discussing how using `repo` helps remember file paths that correspond to Git URLs 53:45 why changing the default branch name from master to main makes Git automation unmaintainable 55:50 `embark-export` in `projectile-find-file` yields a `dired-mode` buffer!!! 56:50 using `m` to mark files in dired-mode and `!` to `cat` "*.proto" files to a single buffer 58:00 rewinding changes to the scratch buffer for a youtube description 1:01:00 done Emacs with org-roam, org-capture and org-refile helps you manage potential tangents ... but you need to know quite a bit before it helps. Getting your Emacs-Fu to "critical mass" can be tough. The Emacs "learning curve" is intense and it's critical for you to ensure that you engrain heatlhy habits as you learn.. Muscle memory is bad and learning to use Emacs requires juggling complexity & tangents with practice & configuration. Some advice for anyone who's beginning to learn Emacs: Do not attempt to learn Emacs without a mentor Find a way to videostream your desktop with a mentor Use multiple profiles, --init-directory and learn about `emacs -q` Use --init-directory and ~/.doom.d to load Doom Emacs Do not use ~/.emacs.d at all Approach learning Emacs Lisp methodically Prioritize learning Emacs-native functionality Understand how using remote Emacs libraries introduces complexity.