My custom package to quickly hide and restore the mode line. Olivetti
does this automatically but I like having no mode line without the
other changes.
Instead of using leader for everything, with infixes, I create custom
definers for each prefix root. This is along with better which key
strings and makes the code easier to read: instead of setting up
several bindings across all namespaces I must define each binding in
its respective leader.
+ save place
+ global auto revert
- +pretty/* functions
+ esup
+ some randomised messages for dashboard footer
+ some eshell functionality
~ disabled ada mode
+ tons of bindings for org tables
Now allows numeric arguments to be passed to the buffer creation
function. This is especially useful for ~eshell~ which allows
creation of multiple instances using a numeric argument: very useful
for managing multiple buffers. It's an optional argument but I err on
the side of caution so by default I'll set it to nil if I don't want
this feature.
+ bindings for flycheck-(next|prev)-error
~ bindings for org mode (now has prefix "l" for links)
~ c(++?)-mode's binding for c-(beg|end)-of-statement now set just for
c(++?)-mode
I really like Eshell. Fanboy a bit about it in my configuration, and
describe its true abilities. Further split up the config so it's a
bit easier to read.
To remove the ~(require 'cl)~ dependency, I wrote my own reduce for
boolean values, recursive, which should do the trick. Mostly just to
remove the annoying "haha no cl library anymore".
Using sly, make a LISP IDE in Emacs. REPL with high level
integration, first class syntax highlighting and error reporting and
an environment literally built out of it.
Always open a new frame when opening link in org-mode: predictable,
safe behaviour which leaves it up to my window manager as to what to
do next. Most of my opened links are files that I want to examine
along with the org file I opened them from: this allows me to do
exactly that.
Set to 4 workers at the start to make compilation at least as fast as
possible: my laptop has 4 cores so it'll just slow it down until early
compilation is done, while my desktop can still keep going as it has 8
threads. In config.org this is setup correctly so the rest of the
config (which is the much larger part) uses a system dependent number
of cores.
