For some weird reason the theme broke. I suspect it is the latest cl-lib
removal, and Nixpkgs is probably not updated with it just yet. So, at
least it is working via Nix for now. Welcome to Emacs, cheers.
This reverts commit adbaa9ebbc.
Turns out, mbsync adds hostname to every mail file. And that makes
things pretty awkward, often syncthing same mail file multiple times.
Since I do not expect to have hermes and phoebe running simultaneously
most of the time, I think it is fine to sync mail to both independently
of each other.
Uses a new app-password, but same name so I don't have to modify the
gmail module.
Oh, also moved hermes/mail.nix to modueles/mail/gmail.nix because now it
is shared.
The new config is much smaller, the new mode uses native tree-sitter
integration, and appears to be actively developed. It does not have all
the features as the doom module, but I didn't seem to use any of it
anyway.
In all the time that I've had Hyperbole installed, I've only ever used
it to open file paths, and only in Nix files. While the package is
versatile and quite useful, it is a heavy package and takes noticeable
time on first start.
OTOH I am just not discovering that the same use-case is covered by
Embark, is much more featherweight in comparison and is already loaded
and used by Doom by default. After trying out, while not 1:1
replacement, it is a good enough one, so I'm removing Hyperbole for now.
The keybindings, by virtue of being probably single most accessible one,
is now awarded to embark-dwim, but may be exchanged with embark-act in
future, depending on how I feel. embark-act gets C-. for now, which
itself is also fairly accessible.
This fixes Jinx marking everything as incorrect spelling problem. The
dictionaries aren't that much different from before, but oh well. I'll
take what is working for now.
While I do like the concepts and simplicity of the language, for my
current goals, something simpler (even if uglier) is better suited. I'll
probably come back to this one later.
The language is way too big for my current free time budget. While I
would have loved to try some newer type theories, perhaps now is not the
best time to go for it.
Since I have nearly never used jq the language and have only ever used
it as json pretty printer, fx is a better and lighter and more nicer alternative.
I like tiddywiki better. It is much nicer to setup, fast and no
bullshit.
For now, I'm keeping 'minio', just in case I have to experiment with S3
compatibility for something, but outline is definitely gone
this allows for better editing experience compared to the stringly mess
from before.
So now Emacs is good for modifying NeoVim config, with support for both
Nix and Lua, and NeoVim is capable of editing Emacs config via orgmode.
Nice :)
So eza aliases will actually take effect.
Eza is supposed to be an experiment. Since I almost always use exactly 3
flags from ls, which I know by heart at this point, I think I can live
with this, but we'll see.
This is primarily there because quite a few language servers are written
using NodeJS (not that I still like that fact..) but since Neovim is my
'fallback' editor, supposed to help with quick edits/fix Emacs config,
LSP is very much out of scope.
Neovim is my fallback editor, when Emacs config is borked. It is nice
(and risky) to mess with this, but I expect Neovim plugins to be
slightly more stable than ball-of-mud that is Emacs runtime.
This gives a nice magit-like interface, a decent mode/statusline, and
enables tree-sitter for all languages, including a decent enough orgmode
plugin.
nvim still launches in less time than I can notice, and since it is
terminal only, I expect to use it much less often than Emacs. But, when
the need arises, it will be nicer than being completely barebones.
P.S. This commit was written from neovim itself, using the fancy neogit
plugin, and I must say, it is noice! Not quite the magit that I'm used
to, but close enough :)
