emacs-package-dev-handbook VS font-lock-studio

Some Elisp libraries already exist that implement CSS/XPath-style selectors. I catalogued some at https://github.com/alphapapa/emacs-package-dev-handbook

Yeah, that's Solarized Dark using https://github.com/alphapapa/org-html-theme-darksun. Looking at your site, I'm thinking that I ought to do a Solarized Light version too. The handbook is also viewable on GitHub, which may be more readable in some ways: https://github.com/alphapapa/emacs-package-dev-handbook

The emacs package developer handbook may have some tidbits of information for you: https://github.com/alphapapa/emacs-package-dev-handbook

Write a few scripts in elisp to get used to the language. Learn various elisp concepts and write programs that use them. Some examples could be to write hooks, learn how to make minor and major modes, make an http request, write macros, make charts, learn how to implement your own version of doctor, tetris, dunnet, or whatever else sounds interesting to you. These could be interesting to look through to see what's out there: https://github.com/p3r7/awesome-elisp#org-mode-outlines https://github.com/alphapapa/emacs-package-dev-handbook

Also found emacs-package-dev-handbook from /u/alphapapa. I haven't looked through it in detail yet, but given his quality of work I imagine it's worth looking into.

I checked the book's TOC and was surprised to see that lexical scoping was introduced in the last chapter.

https://github.com/alphapapa/emacs-package-dev-handbook#lexi... says using lexical scoping is a best practice.

I think you should learn what you want to learn, consult this reference to learn basic syntax and consult the emacs package dev handbook to learn how to use / do certain things.

Sure, see https://github.com/alphapapa/emacs-package-dev-handbook

In general, https://github.com/Lindydancer/font-lock-studio can help.

I am not sure how font-lock works in details, I don't use to tinker with it much, but there is a precedence between font-lock methods keyword-based font locking, function based, in which order they are specified etc, as well as syntax-table and font-lock. Check that something else takes precedence over your properties. You will have to do more research on the subject to sort it out. I am not an expert, I can't help you much more with that, maybe someone else can, but definitely check font-lock docs. As a tip, font-lock-studio is useful when looking at font-lock properties.

Anders Lindgren's font-lock-studio package makes debugging font-lock-keywords easy, allowing you to step through each keyword as a buffer is fontified. In the linked issue, you can see how I used it to quickly find which of the keywords used in git-commit-mode was matching too much. Without font-lock-studio, it would have required tedious testing of each regexp.