Issue overload

[Golmote]

There are currently a lot of open issues in this repository. I'll try to give an overview of the current situation.

Dear maintainers, if you could take a look at this and do some clean up, we could have a clear view of the remaining bugs that need to be fixed :)

Issues that could be closed now

Issues listed here have been fixed already (or will never be as they aren't related to Prism).

• Option to show the language that is highlighted #1 has been fixed thanks to the Show Language plugin.
• How to show EVERY line number? #22 has been fixed thanks to the Line Numbers plugin.
• Javascript variables composed just of letters a-f highlighted as numbers? #74 has been fixed by PR Changed regex Prism.languages.javascript.number #63
• prism-file-highlight.css missing #108 has been fixed by PR Fix fetch of a not existing css file in file-highlight plugin. #119
• Issue with loading download page. #123 has been fixed by PR Issue with loading download page. #129
• When '</' appears in javascript code, it gets converted into html comments #131 is not related to Prism
• Autolinker plugin incorrectly ignores URL fragment identifiers #163 has been fixed by PR Fix Issue #163 Autolinker plugin incorrectly ignores URL fragment identifiers #214
• accessibility? #192 is not a bug
• LaTeX support #206 has been fixed by PR Added initial LaTeX support #316
• SCSS functions not correctly marked #237 has been fixed by commit f81554d
• CSS Extras listing all CSS functions #239 has been fixed by commit d28a9af
• Prism.highlight and Prism. tokenize doesn't work with Prism.languages.markup #250 has been fixed by PR Fix premature HTML encoding #258
• the after-higthligth callback doesn't run #283 should be tagged as #wontfix
• doesn't work at all #339 must have been fixed by PR Fixed missed encode call for webworkers #338
• download buttons do nothing on your website #340 is not related to Prism
• No highlighting option? #344 has been fixed by commit cfaf681
• Autolinker not functioning (on prismjs.com) #359 has been fixed by PR Fix for DFS bug with new pattern array feature #360
• Prism throws strange lines of code  #379 is not related to Prism
• prism doesn't highlight HTML  #394 has been fixed by PR Remove invalid alias declarations, which cause HTML highlighting to fail #395

Other issues...

Finally, these are issues I'm not sure what to do about :

• A CSS/base64 sample hung Safari/Mac #77 looks like a really specific edge case and should probably be tagged as #wontfix
• language-markup is wrong #143 seems to be fixed, but I can't find the exact commit that solved it
• Why only first error shown in file highlight? #152 I couldn't reproduce the issue
• prism should work with languages it doesn't know #181 seems fixed to me (just use "language-none"), but it is closely related to have to add class to <pre> too with WordPress + W3Totalcache #67 which is not fixed.
• Syntax highlighting issue with Git #357 could be fixed by extracting the git language changes from the PR [Git] Add of some jasmine tests #355

[LeaVerou]

Thank you so much for this summary!!! Like I said in another thread, I'm basically off until mid next week, but just wanted to thank you for this effort. You rock!

[Golmote]

Yes, I know you're being busy. I just drop it here so that you may come back here when you have time ! ;)

[vkbansal]

@Golmote PRs are also overloaded

[Golmote]

@vkbansal Yes, I know.

[LeaVerou]

@vkbansal Yes they are, but you’re not helping in any way by asking when they will be merged on a dozen PRs and then complaining here that PRs are overloaded. You’re only making everyone feel bad. If you want things to move faster, contribute more, like @Golmote has been doing.

[vkbansal]

@LeaVerou I'm sorry if I offended you. I did mean to make you feel bad. As for contributions, I know I've been not helping as much as @Golmoye has been because I'm occupied with my porting project. In that process I've found couple of issues and reported them.

My main motive was to give momentum to PRs. Sorry if you feel offended.

[LeaVerou]

I feel offended that what you understood from my message is that I got offended.
Btw, even if I was offended “I’m sorry you were offended” is a non-apology. Keep that in mind for when you actually offend someone. :P

[vkbansal]

My bad. Will keep that in mind.

[Golmote]

Most of the fixed issues have been closed by now, so I think I can close this one too.