just add two spaces at the beginning the search string

Compared to being the kind of person who reads use-package like JSON and treats it like a declaration language, you will be light years ahead at configuration if you just know lists, quoting, alists, plists, and writing functions.

Hey, use-package user here. I switched from my half-baked NIH init framework with a bunch of functions and other stuff you’re talking about, and never looked back.

My 1670kLoC config doesn’t contain any definitions and mostly declarative. If I need to defun something (so, there’s no package with similar functionality) - there’s definitely time to start another package. I don’t even need to publish it on MELPA, since installation from git sources hasn’t been an issue since Quelpa appeared (like 10 years ago).

Users who don’t go at least that far will be constantly shooting themselves in the foot and spending much more time with minor, novice level bugs that are completely obvious.

Debugging use-package forms is very easy if you know about macro expansion.

async-shell-command

I switched to detached-shell-command from detached.el

tab-width command

it’s not a command, it’s a defcustom

add-hooks

aware of use-package?

is-savable-buffer-p

-p suffix already means a predicate, you don’t need is-

also, let evals all bindings, while and is a short-circuit thing, I don’t see any reasons to bind all these, especially is-file-buffer

defvar

most of these look like user-customizable variables, so defcustom should fit better

(when (when

an antipattern, use and

#'(lambda

don’t

also, avoid using lambdas in hooks

defmacro

never ever use macros if a function can do the job

P.S. flycheck-package is your friend

Not related to your question (you’ve got the answer anyway), but you call (handle2 max-time) twice, I’d bind the result in let instead.

who do you need those lots of jobs for?

how is your school going?

For example instead of using projectile or find file inside emacs I can just use fzf from the cli

I don’t see any advantages, only downsides. The great thing about Emacs is the consistency. Autocompletion (ivy/vertico/etc), actions(ivy/embark), help(ivy-rich/marginalia) - it’s all here, with the same shortcuts.

if you already use a graphical terminal emulator - why just don’t use GUI Emacs?