Emacs

cross-posted from: https://lemmy.world/post/14012479

To all evil-mode users, how do you work with vterm?

As a long time Vimmer, I have recently started using Emacs out of sheer curiosity. I chose Doom Emacs as it has evil-mode enabled by default, and do not want to dive down the rabbit hole of configuring the editor from scratch (at least, not yet!).

After installing and enabling libvterm in Emacs, I am having a frustrating experience. I configured ZSH shell to use vi-mode keybindings which interferes with evil-mode whenever I press Esc or C-[.

After having searched a little, I came across a workaround to disable evil-mode when in vterm. But it is still not a smooth experience. For instance, when switching between buffers (C-w C-w).

I would like to know how others in the community tackled this problem. Is there a better solution to this problem? Or have you made peace with the aforementioned workaround? Or have you stopped using vterm entirely?

I'm trying to get out of my Python/Javascript comfort zone and start contributing to other Fediverse projects that are built in other languages. If you are already using Emacs for your dev work in any of the above languages, can you share perhaps your configuration or at least recommended packages for beginners, which prioritize sensible defaults and can be used with minimal amount of fussing?

cross-posted from: https://lemmy.sdf.org/post/10280862

https://protesilaos.com/emacs/ef-themes-pictures

Theme in picture is ef-summer. I love these so much. They're a breath of fresh air among the other techy-cyber-hacker themes, yknow?

The other ones seem less active than this one.

It's gotten too much. I think 1100 is a bit too much custom ELisp code. I also got to a point where my customization started interfering with Doom's core modules, yielded weird errors from time to time. I found out that Doom's defaults are actually beautiful and idk guys I feel refreshed, I'm ready now to get shit done, I can now actually work™️. I have offloaded the annoyances to Henrik.

2024 year of bankruptcy let's go

What's the best practice to have your custom elisp natively compiled, along with external packages?

So far I've only succeeded by doing the following:

• Move my custom elisp to a new file (emacs-lib.el) which starts with (provide 'emacs-lib)

• Manually run emacs-lisp-native-compile-and-load while visiting that file

• Change my init file to load the library:

  (setq elisp-dir "~/config/elisp") (add-to-list 'load-path elisp-dir) (require 'emacs-lib)

After restarting Emacs, I've checked that many of my custom functions are indeed native-compiled.

It would be nice if I could have my init file take care of compiling the library when missing or outdated. Even better if I didn't need the separate file, but that's no big deal.

I wrote a library that lets you cycle through the available themes in Emacs. F10 and shift-F10 keys will cycle forward and backward through the themes. The theme name is printed for reference.

https://github.com/tsengf/theme-cycle

Installation
Download theme-cycle.el into ~/.emacs.d.

Add the following to your Emacs configuration

(add-to-list 'load-path (expand-file-name "~/.emacs.d)
(require 'theme-cycle)
;; Load as many themes as you are interested in exploring.
(use-package doom-themes)
(use-package ef-themes)
(use-package modus-themes)
(use-package solarized-themes)

To Use

Use F10 to cycle forward through the themes. Use shift-F10 to cycle backward through the themes.