oreodave/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Some documentation for config

Browse Source
This commit is contained in:
Aryadev Chavali
2024-10-06 12:30:20 +01:00
parent b309c9c2ea
commit 96d110f4ec
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
Emacs/.config/emacs/config.org
View File

@@ -52,12 +52,12 @@ the idea. I mainly utilise this to explain my decisions for
configuring or using certain packages: Emacs is an opinionated piece configuring or using certain packages: Emacs is an opinionated piece
of software and I may as well express my opinions somewhere. of software and I may as well express my opinions somewhere.
Sections tagged =WAIT= are not compiled and are, hence, unused. Sections tagged =WAIT= are not compiled into the final document and
Usually I provide some reasoning as to why. If using Emacs, the code are, hence, unused. Usually I provide some reasoning as to why. If
in any one section may be loaded interactively (in case I need it using Emacs, the code in any one section may be loaded interactively
immediately). A lot of code here is essentially write and forget; (in case I need it immediately). A lot of code here is essentially
nothing needs to change unless I find a more efficient way to do write and forget; nothing needs to change unless I find a more
things. efficient way to do things.
Some sections border on blog posts justifying why I think they're good Some sections border on blog posts justifying why I think they're good
applications or giving some greater reasoning about my specific applications or giving some greater reasoning about my specific
@@ -2119,9 +2119,9 @@ current working directory.
NOTE: I don't defer this package because it autoloads any eshell NOTE: I don't defer this package because it autoloads any eshell
internals that it uses so I'm only loading what I need to. Any internals that it uses so I'm only loading what I need to. Any
~eshell/*~ functions need to be known by eshell before launching, so ~eshell/*~ functions need to be loaded before launching Eshell, so if
if I loaded this ~:after~ eshell then the first instance has no I loaded this ~:after~ eshell then the first instance has no knowledge
knowledge of the new additions. of the new additions.
#+begin_src emacs-lisp #+begin_src emacs-lisp
(use-package eshell-additions (use-package eshell-additions
:demand t :demand t