Skip to content
#

grammars

Here are 98 public repositories matching this topic...

AccessViolator
AccessViolator commented Feb 24, 2020

Everything in diagrams.css should be scoped to some wrapping css class, because as is it cannot be bundled with the rest of an app's css because of styles like this:

div {
    -webkit-touch-callout: none;
    -webkit-user-select: none;
    -khtml-user-select: none;
    -moz-user-select: none;
    -ms-user-select: none;
    user-select: none;
}

svg {
    width: 100%;
}

Curre

kendonB
kendonB commented Jul 3, 2019

LaTeX is hard for newbies to use. LaTeX is hard for people who have used it for years to use (i.e me).

I propose that we pull a lot of the stuff in CQR out and put it into readthedocs.

The big drawback which would prevent us from doing this for everything is that markdown doesn't do footnotes. However, a lot of the current CQR doesn't have footnotes. I don't think being able to nicely print

Simple, effective, and modular package for parsing observables (indicators of compromise (IOCs), network data, and other, security related information) from text. It uses grammars rather than regexes which makes it more readable, maintainable, and hackable. You can test this project out here: http://ioc-finder.hightower.space .

  • Updated Jul 19, 2021
  • Python

Improve this page

Add a description, image, and links to the grammars topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the grammars topic, visit your repo's landing page and select "manage topics."

Learn more