Include EWS as an Emacs package and include a variable that allows to choose dark mode by default.

[quijote-asim]

Hi Peter.
I wanted to ask you a question and make some suggestions, as I'm just getting used to using EWS without any personal tweaking except for folders.
The question is whether you plan to include EWS as an Emacs package at some point. I think that would make it easier to install and upgrade.
The first suggestion wouldn't make sense if the above happens, but if not, it would be nice if the configuration file was in org mode and generated multiple .el. This would make studying and learning easier.
The second is because my visual impairment causes me to usually work in dark mode. Although the change is easy with the keyboard, just after opening Emacs, I think it would be a good practice to have a variable that allows to choose the default mode.
Thanks a lot and happy new year

[pprevos]

Hi Antonio,

I have removed the line that activates the default theme and then you can set your own theme with the customize-themes command (aa7cd37). Select your preferred theme and click 'Save Theme Settings` so it will start next time.

The new version also installs the EF-Themes package, which provides a nice collection of light and dark themes. Check them out with consult-themes (C-c w t s).

EWS is not intended as a static config with full interactivity and Init files cannot be a package. What will be a future package are the functions in the ews.el file, but that is mere detail.

A configuration file also cannot be in Org mode. There is an Org version in documents/book/99-appendix.org. This file is used to generate the active init file, so there is only one source of truth. After any changes you can 'tangle' the code to the init file. Literate programming is outside the scope of EWS.

Have a great 2025

P:)

[quijote-asim]

Thanks to you for your prompt and clear response.

EWS is helping me a lot to organize myself and if I may, I would say that I miss in the book a chapter dedicated to the org-mode agenda, which I know is somewhat complex and very personal and a Hugo section in the publishing chapter.

It's a topic that I can't get to grips with due to my lack of web knowledge, and although I manage to create the site on my PC I still can't figure out how to put it into operation in GitLab, but I'm still working on it.

Best regards

[pprevos]

I decided to only include a standard Org agenda because developing one requires Elisp knowledge. The intent of the book is to teach Emacs without Elisp knowledge. This video explains it very well: https://www.youtube.com/watch?v=-9rpQA6O3aM

Not sure how that relates to GitLab. I don't know much about publishing website sites with GitLab. I think the key is the .gitlab-ci.yml file.

The reason I left out Hugo is because it needs some workarounds. Also, publishing to the web can be technical and there are many methods. Happy to help via email and then based on your questions I can update my web page on Hugo.