search

jgm / skylighting

A Haskell syntax highlighting library with tokenizers derived from KDE syntax highlighting descriptions
190 stars 61 forks source link

Added *.el to commonlisp’s extensions #86

Closed NightMachinery closed 1 year ago

jgm commented 5 years ago

Isn't .el emacs lisp, not commonlisp?

NightMachinery commented 5 years ago

Indeed, but us poor elispers are better off with commonlisp’s highlighting than no highlighting at all. (Unless there is elisp highlighting? I didn’t see one ...)

On Tue, Aug 20, 2019 at 11:27 AM John MacFarlane notifications@github.com wrote:

Isn't .el emacs lisp, not commonlisp?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jgm/skylighting/pull/86?email_source=notifications&email_token=AIUL56Q3TTADPBCCCRN7PMDQFOIXLA5CNFSM4INPWV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4VIV5A#issuecomment-522881780, or mute the thread https://github.com/notifications/unsubscribe-auth/AIUL56QHOC45GEOF7S2ZCGLQFOIXLANCNFSM4INPWV5A .

jgm commented 5 years ago

Yeah. I suppose nobody would use the Kate editor to edit emacs lisp, so nobody bothered to add a KDE syntax description for it.

I think a better solution would be to add an elisp.xml syntax description, which is actually tailored to elisp. It could also be submitted upstream.

NightMachinery commented 5 years ago

Yes, but I’m not familiar enough with either elisp or KDE syntax descriptions to do that. If someone is not going to do that, please merge this in for the meantime. Perfect is the enemy of the good.

On Tue, Aug 20, 2019 at 11:14 PM John MacFarlane notifications@github.com wrote:

Yeah. I suppose nobody would use the Kate editor to edit emacs lisp, so nobody bothered to add a KDE syntax description for it.

I think a better solution would be to add an elisp.xml syntax description, which is actually tailored to elisp. It could also be submitted upstream.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jgm/skylighting/pull/86?email_source=notifications&email_token=AIUL56TW7EG2JPECLN3622DQFQ3SHA5CNFSM4INPWV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XJDEY#issuecomment-523145619, or mute the thread https://github.com/notifications/unsubscribe-auth/AIUL56QGO4IFVZKEPV66XBTQFQ3SHANCNFSM4INPWV5A .

jgm commented 5 years ago

Well, for now you can use your own version of commonlisp.xml using the dynamic loading feature.

NightMachinery commented 5 years ago

What’s this dynamic loading? Note that I’m using pandoc, and not skylighting directly ...

On Wed, Aug 21, 2019 at 8:40 PM John MacFarlane notifications@github.com wrote:

Well, for now you can use your own version of commonlisp.xml using the dynamic loading feature.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jgm/skylighting/pull/86?email_source=notifications&email_token=AIUL56VBBFWVV4K6WRNW24LQFVSF3A5CNFSM4INPWV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42GVSI#issuecomment-523528905, or mute the thread https://github.com/notifications/unsubscribe-auth/AIUL56VHOHMU5T4GINVQ2NLQFVSF3ANCNFSM4INPWV5A .

jgm commented 5 years ago

With pandoc, check out the --syntax-definition option.

jgm commented 1 year ago

fixed upstream and in skylighting