Updated March 18, 2021
Most of my code has changed a lot recently. Check updated posts.
For each post can update code listed in that post. Keep in mind code for linux and wsl configs will have their own posts, except in the case of .early-init and init.el, which have system switches (to load system specific dot-files).
Also note: abandoned convention of listing init lines. Now if you want to find the code, and there is now plenty of decent emacs code, use the search function. The site is not large.
Defvar vs setq
Defvar includes messages, and in some cases combines with :custom in use-package to add additional functionality. I replaced in my init all instance of defvar with setq.
Also, no longer require paths to libraries as properly configured the load path see post: Emacs Configuration Overview.
Original Post Below
Directly below are the subheadings to the first main heading of my initialization file, see my last post Emacs Configuration Overview.
Directly below are the subheadings to the first main heading of my initialization file, see my last post Emacs Configuration Overview. I'll go through the lines of code in order, but remember, the line numbers you see in Hugo's code block css styling are relative to the code on this page not the emacs initialization file [Hugo is the Static Content Management System based on GO I used to make this blog]. There are roughly 760 lines of code beneath these subheadings (all of it quick and dirty). I'll go through the relevant stuff and skip anything redundant in this post and the next few. Each post will have the following reference headings, and then the breakdown and write-up below that.
Beginning of Initialization File
- SET UP, DEFAULTS, AND CUSTOMIZATION
- Necessary Adjustments when you set-up on a new computer
- Paths to Update on Change
- Executable Paths
- Libraries
- Function declarations
- Emacs Customization Seperate File
- Emax Defaults
- Some Defaults
- Frames, Buffers, And Lines
- Some Custom Default Functions
- Some New Key Bindings
- Popup, Pos-tip,Tooltip, Posframe
- Which Key
Oh yes, when I installed the dashboard package there was an option to choose a picture. That's when I named my Emacs configuration. Welcome to Poseidon the text editor.
Necessary Adjustments when you set-up on a new computer
steps needed to get set-up on a new computer
- install emacs
- install external executables
- paste .emacs and myinit.org from active emacs installation to new emacs installation
- Change load paths in myinit.org
- paste dependency folders to new emacs (snippets, etc.)
- adjust home variable on new system
- adjust emacs to have administrator rights
- restart emacs and deal with each error as emacs runs through myinit.org code (Most errors should be easily resolved by updating directory paths, providing missing libraries, ensuring executables and missing library dependencies are installed)
- to troubleshoot basic errors use emacs debugger, messages, and the restart-emacs package. Also, comment out org tangle blocks and initialize the init incrementally.
Paths to Update on Change
Here paths to executables, libraries, and external urls are stored in variables. When you install Poseidon on a new system, or change a program or its location, change the path variable assignments here. Later in the code, usually in a use-package :config or a function the variables are called.
Oh, btw, before the path assignments is an org-tangle block, delineated by the org-mode elisp code on lines 2 and 4. Everything inside them is processed by emacs, everything outside is notes and text you can push to the web easily.
| |
So there's the first 130 lines or so of my init file (52 shown here plus the paths I didn't bother to paste in and some text). Btw, it doesn't matter where you store your stuff, as long as emacs knows where it is. In fact, that's the point of assigning the paths to variables. When your paths or path names change, you don't have to search the document for each path. Coming up are the function declarations.
