solarized-emacs VS use-package

I can confirm that the name of theme is solarized-selenized-white which included in solarized-theme.

Solarized Light (with Noto Sans Mono)

There is no reason to watch videos, it will be self-explanatory when you use it; you can't miss it. Once you have three or more windows in Emacs it will show you a number, just press the number, and it will switch to the window. If you install a nice theme that has theming for ace-window, such Batsov's Solarized (or any of other derivatives), you will get nice theming for those numbers, so they stick out too.

The first one looks like a version of solarized. I think I have seen some other screenshots of him using something similar to Solarized dark, but I don't know for sure. At least I see Batsov's solarized forked on his account.. I don't know if he has done any changes, I think he did, since his color scheme does not look same as mine, and I use same theme unchanged from Batsov. Those other themes can be just different color schemes that comes together with Batsov's port of Solarized (zenburn, etc).

Everything feels quite well integrated to me. I also use Solarized by Batsov which minimizes the rainbow of colours that some packages introduce, notably. Most of the time I use two windows side by side in Emacs, so *-dwim commands can auto guess when I copy/move some file.

For the looks, if you don't like built-in themes, I suggest you some of Batsov's themes. I am using his Solarized port, and I recommend it because he has gone to great lengths to customize external packages, which can give you a more uniform look with third party packages out of the box. You don't need to use the solarized color scheme, there are other color schemes included there. It might help you with looks of tabs. I don't use tabs myself, but I wouldn't be surprised if he has taken care of tabs look too.

That's how a lot of themes work. Bozhidar Batsov's version of Solarized has a slightly different approach to file organization:

Another way would be to redefine parts of the bind-key macro or its use-package support functions

The package-install call installs use-package that provides a utility of the same name to make it easier to manage packages. It's admittedly a little overkill for this specific config, but it's a cheap investment that sets you up for later success.

Granted, the Doom macro makes your code looks nice and compact. But you can get very close to that just by using do-list and define-key together. Or by using the bind-key.el package, which is included with Use-package.

> Deps is well documented.

> The issue I personally found is that I needed to look at a bunch of OS project's deps.edn to see how people commonly structure things. Other than that it is a simple tool.

This strikes me as a contradiction, because if it was well documented you wouldn’t need to look at other people’s configs to see how to use it.

My experience with deps.edn is that every time I start a project and make a deps.edn file, I immediately draw a blank and don’t know how to structure it, so I open ones from other projects to start lifting stuff out of them.

I still don’t know how to reliably configure a project to use nrepl or socket repl without just using an editor plugin. I definitely have no idea how to use those in conjunction with a tool like reveal.

To me, none of that is simple. Simple would be like Emacs’ use-package. With that I know how to add dependencies, specify keybinds, and do initialization and configuration off the top of my head. And it has really nice documentation with tons of examples.

https://github.com/jwiegley/use-package

Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).

I'm using use-package as my package manager and the package ligature for the ligatures.

I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.