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

Syntax highlighting preview isn't available for local builds #166

Open
hinerm opened this issue Jun 11, 2021 · 2 comments
Open

Syntax highlighting preview isn't available for local builds #166

hinerm opened this issue Jun 11, 2021 · 2 comments
Milestone

Comments

@hinerm
Copy link
Member

hinerm commented Jun 11, 2021

When using code fences (``` ```) we do not see code syntax highlighting when building locally. This has something to do with using jekyll 4.2 directly instead of the gh-pages gem. It would be nice to have this preview.

In the interim, adding a note to code editing.

@hinerm hinerm added this to the post-production milestone Jun 11, 2021
@mattxwang
Copy link
Collaborator

Hm interesting, I can't repro this issue locally - is there a specific set of steps I should take?

@ctrueden ctrueden modified the milestones: post-production, unscheduled Jun 14, 2021
@ctrueden
Copy link
Member

ctrueden commented Jun 14, 2021

It doesn't work for me locally, either. I tested the following setups:

  • Ubuntu 20.04 with Firefox
  • Ubuntu 20.04 with Chromium
  • macOS Big Sur with Firefox
  • macOS Big Sur with Chrome
  • macOS Big Sur with Safari

None of these highlight colors on the first code block of develop/debugging, but do highlight them on the live site.

@mattxwang Is it possibly because you're using Ruby 3 rather than Ruby 2.7? What's your browser + OS?

I tried adding all the missing gems from the gh-pages-based Gemfile to a 4.2-based Gemfile, to see whether that would magically make the code-fences-based code blocks start highlighting successfully in the local Jekyll installation. Unfortunately, no dice. I'm not sure why 4.2 doesn't highlight code fenced code locally. But the fact that it does it successfully on the live site is good enough for me, for now. This issue is definitely low priority in my view.

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

No branches or pull requests

3 participants