Philip Kaludercic <philipk@posteo.net> writes:


[...]

> --8<---------------cut here---------------start------------->8---
> [package avy]
> set all-windows all-frames
> bind C-z avy-goto-word-1
>
> [package auctex]
> set TeX-master dwim
> hook TeX-language-de-hook site/use-german
> rebind RET newline 
>
> [package bash-completion]
> (bash-completion-setup)
> --8<---------------cut here---------------end--------------->8---
>
> where the common patterns are simplified and made safe (e.g. the "set"
> directive wouldn't evaluate) but still remains powerful, as you can
> intersperse lisp code.  If I ever get around to finishing this -- or
> anyone else decides to steal the idea ;) -- then adding this to the core
> and loading ~/.emacs.d/init.conf if it exists might be a useful thing to
> mention in a newbie manual.
>

Using non-lispy language for configuring Emacs wouldn't be appropriate,
as it could make using emacs lisp intimidating.  It would be preferable
to gently guide and support a user in their first steps with setting up
emacs, using emacs lisp, to help them accomplish their tasks
effectively.

A better option might be to adopt a system similar to =doom!= macro that
enables "modules" in Doom Emacs for OOB experience (e.g., Python
development, emails etc).  Additionally, a web page or wiki detailing
recommended packages and their use-package snippets for various
programming languages and tasks that emacs developers use & recommend
would be helpful, even more than a getting started guide.

I should also note that the info pages are really well done & the code
that is written in emacs is well documented for users eager to delve
deeper once they're more confident.  However, reaching that point can be
daunting.


-- 
Thanos Apollo
https://thanosapollo.org