~highlight is now a darker face of gray, region is lighter
+org-verbatim & org-code faces so they are more distinctive
+haskell-interactive-face-prompt for aesthetics
The dashboard is the first thing I should see when entering Emacs,
hence I should demand the package instead of deferring it. Doing so
means that dashboard is loaded instantly and will generate the
=*dashboard*= buffer, which I can set =initial-buffer-choice= to be.
Even though I've stopped using doom, I keep its config in case I may
need to dig through it (though I haven't for a good while).
Nevertheless, I didn't update the links to the README which I felt is
bad code-keeping.
hlight alias highlights words via grep. Basic usage is for files but
can also be used for piped input. Just a bit nicer to use.
zsh history management makes zsh-fish-autocomplete an even more
powerful tool (as it now has a giant history to read through instead
of just a local history)
=counsel-unicode-char= has been bound to "<leader> ic" which allows
me to use TeX and other unicode symbols without switching to the TeX
keyboard. =yas-insert-snippet= has been bound to "<leader> ii"
There was a split in namespace across my config: "+dx/" or "dx:".
"dx:" was used for older functions created near the start of this
config, while "+dx/" is used basically everywhere else and is my
preferred namespace for new functions. Hence I resolve this conflict
in this commit.
Personal theme doesn't work on such a low transparency (I chose
colours that are less vibrant and poppy, going for a low-key theme)
hence set the alpha higher.
Don't even remember when I changed theme but it's gone back to
personal (my custom theme). I changed a few things for the theme as
well, just a few colours.
(Shell)~propagate change to emacs service (no -s MAIN) and editing
(XServer)~state explicit full path for lock script for ease of
understanding (it's a user script, not some other program)
Just some code to make editing in the Haskell REPL a nicer
experience. Allows me to write multi-line code in a separate buffer
with haskell-mode switched on, then with a simple keybinding paste and
evaluate the full code in the Haskell REPL. The keybindings and
workflow are similar to org-src block editing (create a new buffer,
then paste the contents back into the original buffer).
(Emacs)~changed some descriptions, formatting, edits of assigned
functions
(Scripts)~allow psearch to use all arguments supplied rather than just
the first one (pacman -Ss actually greedily consumes all arguments
given as part of the search)
The .config folder stores the configurations generated by various
packages. For the purposes of cleanliness and also generalisation I
might as well VC it.
+psearch function to search pacman with less (I use this all the time,
just makes it easier to do in one go)
~speed script to use a slightly larger file so user can get a better
estimate of dl speed
~ada-mode slightly better comments
In hindsight, what other daemon am I going to be using for Emacs?
It's not like I'll be starting two different servers! Even if I was,
Emacs has the ability to assign a new unique name for the server
depending on if another server is already running. Also, having a
name for the main server makes it harder for other services (such as
notmuch-mua.service) to find your Emacs instance.
~changed unicode true
~minor edits to text
~org-imenu-depth is set higher so it can be substituted for org-goto
-+autotyping/gen-skeleton-abbrev as I'm using yasnippet now
I've re-enabled yasnippet for ease of use, and added a ton of snippets
directly into my Dotfiles so only I get to curate what snippets are
removed. Screw downloading them off someone else's repository at
their total mercy.
Each config file is loaded in gamepad-daemon, general then typing then
media. Each profile is pretty self explanatory, and allows for
splitting of responsibilities. Config switches occur through the
guide button.
Xbox controllers are cool, and the ton of buttons allow for a lot of
customisation and ease of use. Hence I created an xboxdrv
configuration which has the standard mouse capabilities as well as the
ability to access an on screen keyboard and some basic media
manipulation capabilities. This is mostly for when I want to sit back
and just CONSOOM content rather than do actual work (hence trying to
remove the keyboard).
My desktop uses VGA and display port for it's outputs, distinct from
the Laptops outputs. Hence we can setup all xrandr records in one go
and be fine for the ride.
The PS1 variable has been changed to look a bit nicer, added some nice
functions for quick edits in the terminal (though I still expect to
use Emacs for anything above a quick edit)
By reinstalling arch on my laptop, I've had the chance to see any
loose ends or errors in my setup that, by virtue of how fresh the
system is, I'm motivated to fix.
