Implement highlighting of Emacs Lisp keywords

[kaushalmodi]

Hello,

Can the emacs-lisp keywords also be ported from Pygments lexers/lisp.py?

Live example: https://scripter.co/building-org-development-version/#set-the-correct-paths-in-your-emacs-config

Here we see that keywords like defvar, with-eval-after-load, unless, .. do not get highlighted at all.

[kaushalmodi]

Here's a screenshot of how the syntax highlighting looks from within Emacs:

Also note the special highlighting of symbol in `..' within the docstrings and comments .. like `lispdir', `infodir'.

[alecthomas]

You'll need to use the same theme to compare.

[kaushalmodi]

Sorry, the two screenshots were not for theme comparison.. they were to show that:

• The keywords like defvar, with-eval-after-load, etc. should be highlighted.
• special highlighting of symbol in `..' within the docstrings and comments .. like `lispdir', `infodir'

Comparing emacs.go with lisp.py, I see that the whole section of keywords/identifiers/macros/builtins is not ported over.

[kaushalmodi]

From the site HTML, I see that the keywords, variable names, etc., all get classified as <span class="n"> .. </span>.

[alecthomas]

Okay. The converter script can only convert RegexLexers. It's likely that the lispish ones are slightly different and will need some manual intervention. I will get to this, but probably not for a few days. If you'd like to send a PR I'll happily merge it.

[alecthomas]

Yes, this is happening because of this function in Pygments. It will need to be ported.

[alecthomas]

Okay, this seems to have worked. Here's your example code highlighted. Note that whether a particular element is highlighted also depends on the style used.

[alecthomas]

Note that I only converted EmacsLisp. The other lisps will need similar treatment.

[kaushalmodi]

Wow! Thank you for implementing this so quick, especially when you apparently don't use emacs-lisp. I'll rebuild Hugo with latest Chroma as soon as I get to my computer.

Apologies for not providing the raw emacs-lisp code for testing. So thank you for going the extra mile to parse the raw code out of that HTML, or finding out the markdown source. I'll make sure to link the source too, next time.

For now, emacs-lisp is the only Lisp I use. So I am content :)

Many thanks again! I'll try it out as soon as I can today, and report back.

---

Final nitpick: Can the emacs.go be renamed to emacs-lisp.go? If not that, then emacs_lisp.go or emacslisp.go? Thanks!

[kaushalmodi]

I confirm the fix. Thank you!

From: https://scripter.co/building-org-development-version/#set-the-correct-paths-in-your-emacs-config