HRhrldcpr·Sep 7, 2022Submission
Rouge syntax highlighter removed support for Solidity “pyramid scheme”
8 points · Open discussionrouge-ruby
rouge
Ruby2014–2022
rouge-ruby / rouge
rouge
A pure Ruby code highlighter that is compatible with Pygments
6Distinct people
7Mentions
0Explicit recommenders
3.5KGitHub stars
What to know before exploring
What it is
A pure Ruby code highlighter that is compatible with Pygments
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2014-12-26 15:30:04 UTC to 2022-09-07 00:25:58 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
7 sources> It's confusing you're replying to two different threads in this
I get that, which is why I specified what it was I had replied to in order to clear it up.
> That's for you. I want to open a huge XML file and edit it with autocomplete.
That's fine. My editor is for me, not for you. To me, if you have to do bracket matching on a 2GB XML file an editor is the wrong tool. I'd work with that in a REPL. But that's me. You're totally free to pick your editor based on the need to handle 2GB files, just as I'm free not care one iota about opening 2GB files.
Hence my point that a lot of people don't seem to think about whether or not they actually need this. I decided I don't need it, and it let me simplify things a lot. It won't work for everyone, and that's fine.
> I mean you could just say. I'm ok with Notepad. Ok. Sure. I'm not.
Well, if I'd
Read the rest
been ok with notepad, I'd have used notepad. I wrote my own editor because I'm not ok with Notepad. Or Emacs. The tradeoffs I care about are very different.
> Any naive approach is going to run into edge cases quickly[1]. Any more sophisticated approach is going to run into performance issues.
For large files, yes. It's more than fast enough to run just fine - even in pure Ruby - on files of the sizes I pointed out are the sizes I've decided I care about.
> [1] For example using regex to color syntax. Reasonably fast yes, but fails in any moderately complex scenario.
Which is why I'm using Rouge for the syntax-highlighting for my editor. It uses Regex for low level lexing where people choose to, but it supports state machines and multi-layered lexing or your own custom code. It supports all the languages I care about and dozens more just fine. My approach of caching the lexer state works just fine with Rouge and the approach I've outlined to e.g. parse my Ruby code with a precise Ruby mode, switch to a Markdown mode inside comment blocks, and feed the output of that into a layer that applies further custom rules based on my preferences. All without needing to build an AST for any of those.
> I suspect it will break waaaay before that. Even using some language with greater complexity would cause issues.
It handles every language supported by Rouge [1] just fine, and that's far more than I have need for.
[1] https://github.com/rouge-ruby/rouge/blob/master/docs/Languag...
Looks like a bug with Cyrillic character highlighting. I'm guessing this is probably an issue with Rogue/Pygments[0][1] since I doubt Github is rolling their own syntax highlighter.
[0]: https://github.com/jneen/rouge
[1]: http://rouge.jneen.net/pastes/6nDQ
In SHA-1 Collision Detection on GitHub.comProperly assigning IP rights is very important to us and it is hard to get right. This is standard language to ensure it is taken care of.
If you have side projects (many of us do, for example https://github.com/jneen/rouge is maintained by our team member Jeanine Adkisson) we recommend you email us the name to have an granted exception on record. If you want we can also add it to your hiring contract. We never declined such an exception.
But if there is an IP lawyer that wants to make an alternative proposal for this language we're all ears.
In GitLab reinstates list of servers that have malwareThanks for using GitLab and for your feedback.
1. GitLab uses the awesome Rouge library to do syntax highlighting, this does support R https://github.com/jneen/rouge/blob/master/lib/rouge/lexers/... but apparently Rmarkdown is broken. I hope someone will contribute this to Rouge.
2. If you want to display the projects publically please make them public. If I misunderstood please let me know.
3. Please email support@gitlab.com about the broken group image and reference this comment. I'm sorry it is not working.
4. Relative links took a lot of work but I didn't hear any complains in the last few months. If it is not user error please open an issue.
5. If you self-hosted installation thrashes consider switching to the Omnibus packages (if you haven't done so already) and increasing memory. For memory requirements please see https://gitlab.co
Read the rest
m/gitlab-org/gitlab-ce/blob/master/doc/inst...
Thanks again for your comment.
Rouge: A pure-ruby code highlighter that is compatible with pygments
2 points · Open discussionAuthor here.
It doesn't use highlight.js. It highlights code on the server side using rouge gem. https://github.com/jneen/rouge
In [dead]