Oops, sorry, muscle memory had me doing C-c C-c on the checkboxes -- which is message-send-and-exit in mu4e. :)
Real answers below. Christian Moe <[email protected]> writes: >> * The survey proper >> Please tick the option that applies to you best in each of the sections. >> >> Basics: >> [] I understand emacs-lisp and can write my configs from the >> documentation provided >> [x] I copy and paste (emacs-lisp) configs and could slightly modify >> them to adapt them to my needs Since you want one option. I do understand elisp and write configs as needed, but I always prefer to copy-paste from people who know what they're doing and have already worked out how to do it. This goes double for LaTeX config, as I don't know LaTeX well. >> [] emacs-lisp, no please >> General font config: >> [] I want my configurations match the manual(s) of the package(s) I use as >> much as possible. >> [x] I prefer to have an abstraction that can be used independently of the >> font/language package I use. Not sure. I only use LaTeX via Org myself, so I'd mostly prefer to have to think about it as little as possible. In particular I want fonts to just work. But I can see how an abstraction might be harder to work with if I want to copy-paste a LaTeX setup or do something differently, and if e.g. the order of latex headers matters. >> Language codes: >> [x] I'm comfortable enough with the language codes used by org-mode >> [] I'd rather use the language names/codes from my font/language package of >> choice. Standards for the win, 100%. I don't want to have to know if it's =slovene= (babel) or =slovenian= (polyglossia). Not to mention =norwegian= and =nynorsk= (babel, variants: norsk, norwegianbokmal, norwegiannynorsk -- babel really lives up to its name here) or =norwegian[variant=nynorsk|bokmal]= (Polyglossia). And those are just two languages I use every day. >> Thanks for any input. >> /PA >> >> PS: A third survey will be following shortly for people who have dared to >> try out the feature branch.
