Idea: Add a popular or likely config option to tune auto-detect

[joshgoebel]

What if someone could configure their Highlight.js as to which languages were "more likely"... so you could tell it that 10-20 languages (or even 1-2) were likely or popular while you supported highlighting for additional ones.

Languages that were likely would get say a auto-detect boost over "non-likely" languages... so if you mostly blog about Ruby but you're always getting flagged as Elixir you could just say that Ruby was likely and boom, problem solved.

This is kind of an extension of "ignore for autodetect' which I think we already have?

[joshgoebel]

My other thought was a callback to allow users to build this type of thing themselves... so you could specify a callback and when auto-identifying if a match was "close enough" it would call your custom function with the raw data and let it decide which was which.

[joshgoebel]

Closing this as it got no discussion and it would be hard to decide this globally in any case. Still a reasonable plug-in perhaps.

Also, if a given language was truly obscure I think we should just consider turning off auto-detect for it entirely.