If I have a bug, let's see if we can keep going.

This commit is contained in:
Howard Abrams 2023-04-03 09:24:52 -07:00
parent 1884e60275
commit 2012a466c4
2 changed files with 3 additions and 2 deletions

View file

@ -244,7 +244,8 @@ With this function, we can test/debug/reload any individual file, via:
(interactive (list (completing-read "Org file: " (ha-hamacs-files :all)))) (interactive (list (completing-read "Org file: " (ha-hamacs-files :all))))
(let ((full-file (f-join hamacs-source-dir file))) (let ((full-file (f-join hamacs-source-dir file)))
(when (f-exists? full-file) (when (f-exists? full-file)
(org-babel-load-file full-file)))) (ignore-errors
(org-babel-load-file full-file)))))
#+end_src #+end_src
And we can now reload /all/ startup files: And we can now reload /all/ startup files:

View file

@ -751,7 +751,7 @@ The idea of linking org documents to email could be nice, however, the =ol-notmu
:straight (:type built-in) :straight (:type built-in)
:config (add-to-list 'org-modules 'ol-notmuch)) :config (add-to-list 'org-modules 'ol-notmuch))
#+end_src #+end_src
To use, read a message and save a link to it with ~SPC o l~. Next, in an org document, create a link with ~SPC m l~. Now, you can return to the message from that document with ~SPC m o~. Regardless, I may need to store a local copy when I upgrade Org. To use, read a message and save a link to it with ~SPC o l~. Next, in an org document, create a link with ~, l~. Now, you can return to the message from that document with ~, o~. Regardless, I may need to store a local copy when I upgrade Org.
* Display Configuration * Display Configuration
Using the [[https://github.com/seagle0128/doom-modeline][Doom Modeline]] to add notifications: Using the [[https://github.com/seagle0128/doom-modeline][Doom Modeline]] to add notifications:
#+begin_src emacs-lisp #+begin_src emacs-lisp