Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix language correcting script #82

Merged
merged 2 commits into from
Jan 22, 2016
Merged

Conversation

syohex
Copy link
Collaborator

@syohex syohex commented Jan 21, 2016

  • Original code does not return language list. It returns value of kill-buffer
  • Original code ignores language which contains space like 'Emacs Lisp'
  • Replace space with '-' like 'Emacs Lisp' -> 'Emacs-Lisp'

And update language list.

This is related to #72.
CC: @blaenk

- Original code does not return language list. It returns value of
  kill-buffer
- Original code ignores language which contains space like 'Emacs Lisp'
- Replace space with '-' like 'Emacs Lisp' -> 'Emacs-Lisp'
@syohex syohex changed the title Fix language corrcting script Fix language correcting script Jan 21, 2016
@blaenk
Copy link

blaenk commented Jan 22, 2016

Good work!

@jrblevin jrblevin merged commit 846a2d0 into jrblevin:master Jan 22, 2016
@jrblevin
Copy link
Owner

Great, thanks! I only have one question: Does GitHub expect or require the spaces to be replaced by hyphens? In my limited testing, it seems so. For example, blocks beginning with Emacs-Lisp` are highlighted but those beginning with Emacs Lisp` are not. I can't find this documented anywhere though...

@blaenk
Copy link

blaenk commented Jan 22, 2016

This seems to show that hyphens are indeed used.

@syohex syohex deleted the fix-lang-script branch January 22, 2016 03:57
@jrblevin
Copy link
Owner

Thanks for finding that! I think the patch is probably good as is then.

After experimenting some more (in comments), it seems that to use spaces you have to enclose the language name in braces, like this ```` {Emacs Lisp}`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants