SolCaronte's Sunny Boat

My Emacs configuration has reached 300 lines and will soon be ready for use on all my machines. I am still having an internal debate with myself about whatever to use the evil keybindings or Emacs key-chord system. I am slowly getting used to the latter, so a switch is likely. The only thing I still need to discover is how to make emacs (or emacsclient, whatever), spawn as a GUI on TOP of a terminal instead of at the side. Yes, I could simply search files from Emacs itself, but sometimes I am browsing around my terminal and I want to make quick edits to stuff, so it can get a bit annoying.

Regarding Light Theme/Mode, I have become used to it as much as I had with Dark Theme. However, I have not seen any sort of differences in regards to how my eyes feel or how easy it is to read stuff compared to Dark Mode. Some people say Dark Theme is better for eye strain, some say Light Theme is better because you don't have to strain your eyes to read on a black background. Or that Dark Theme is better at night because it gives off less blue light and yadayada.

Personally, I think that unless you have some weird eye problems like astigmatism, Dark Mode should be just fine. And, you know, at least on phones and some DEs you can filter-out blue light on the settings if that's what you're worried about. Honestly, perhaps the better solution would be using settings for Light/Dark theme at certain times of day.

As terrible — horrible, abominable — as it is, I have become used to Emacs keybindings. I like them, even. One could even go as far as to say I like them more than Vim keybindings. I still use Emacs as my main text editor, and I like how easy it is to do everything from it (terminals, file managers, etc). I have also gotten used to Light Theme on all my devices, and using Dark Theme now feels kinda weird and hard on the eyes.

I feel dirty and disgusted with myself. I loathe the face that stares back at me in the mirror — I hardly recognize it.

In other news, I have made my own Emacs configuration and am almost ready to ditch Doom Emacs. Do I still recommend Doom? Yes, I think it is a very good starting point, and very easy to use too. For now, I shall continue to configure Emacs and test out all the funny packages in it like Hydra, which has a very cool and epic name tbh.

I have ZERO clue as to why some random-ass internet provider in the middle of fuck-ass nowhere Argentina prevented any SSH connections inside their networks — leading to my great and tragic disappearance for several days until I figured out I only needed to use a VPN. Fancy.

In other news, my Light Theme "experiment" is going nicely! I finally adjusted to them and I feel basically the same as I did with dark mode, perhaps even a little bit better in regards to reading on my phone while out in the sunlight. Emacs, as well, has proven to be a very nice editor all things considered as I've recently taken to making small projects in PureScript. LSP works great, Treemacs does too, and vterm is really useful to keep everything inside the programming environment. I'll likely update more frequently now that I am not chained by obscure internet restrictions. Until next time!

While continuing on my journey of using Emacs as my main editor, I read some papers regarding the differences between Light Mode and Dark Mode in computers. Apparently, Dark Mode isn't all that good for people with certain kinds of eye defects such as I! Thus, I decided to put this to the test, and switched ALL of my graphical applications (Emacs and my phone included) into Light Mode.

One of the first things I noticed is that apps such as Discord put Light Mode in as kind of a afterthought - it's bad, straight up. Certain things look like absolute ass in it, but at least it's not "terrible". Most other applications work just fine, such as Emacs, and I'm starting to get used to it. I think Light Mode gets a really bad rep, but I suppose most of the fault comes from goblins who have never seen the light of day on their lives.

I'm still trying out Doom Emacs as my main text editor for a while, and workspeed has been greatly improved after discovering how to PROPERLY use emacsclient from dmenu. I am still unsure as to how to do certain things like open up files from within the terminal with emcas with having it create a brand new separate window at the side, although I SUPPOSE I could just use dired/dirvish instead of browsing files directly from the terminal instead of inside Emacs.

There's still much to learn, and I'm not giving up just yet.

I've been playing around with vterm in Doom Emacs, and it is PRETTY nice as far as terminals go. Besides that, I've simply been configuring stuff like ispell, writeroom-mode and trying to keep my config pretty minimal. I still haven't gotten writeroom-mode exactly as I want to, but I'm getting there, I believe.

It still won't replace nvim as my primary editor for the time being, but it's getting close to being a really good GUI text editor.

I've recently been toying around with Doom Emacs, and finally managed to properly setup and use emacsclient (even alongside dmenu!). I am still not really happy, however. While Doom Emacs is good, it has its flaws:

• It has a lot of stuff inside it that I just don't use
• It puts layers on top of base Emacs stuff that just really make it hard to configure
• Makes it hard to truly configure your own Emacs - at least harder than just base Emacs

Still, its better than stuff like Spacemacs (yuck), and way better than 99% of Neovim distros.

I've returned to the writing scene after a long absence and so far so good! Been moving out of my comfort zone by writing dark science-fiction and it's going pretty well. Other projects include making a small text-based game on either Python or Twine and finding a way to use Arc Browser on Linux because damn, that shit looking good.

After spending the entire goddamn day on the computer, I have finally migrated from packer.nvim to lazy.nvim to obtain 30ms of startup time.

Was it worth it? I don't really know. I can't exactly tell the difference. Should I have stayed with packer? Maybe, but I don't exactly regret migrating, since I ended up fixing/improving a lot of stuff on my original config. I guess its nice-er to use than packer, with its Mason-like interface, but that's about it. The method to configure plugins is confusing as hell, and the fact was 99% of plugins don't have an installation copy-paste for lazy like they do for packer doesn't make things easier. Perhaps it was a waste of time. Perhaps not. Only time (using nvim with lazy) will tell if I stay or switch back to the safe embrace of packer.

New note-taking system has been working wonders! Now that I have that mess cleared up, I'm between migrating from packer to lazy.nvim or making my own Emacs config from scratch (instead of using Doom Emacs) to see if I end up hating it less. Only time shall tell.