|
20 | 20 |
|
21 | 21 | <style> |
22 | 22 | td.na { |
23 | | - background: #F4E5E5; |
| 23 | + background: #F4E5E5; |
| 24 | +} |
| 25 | + |
| 26 | +@media print { |
| 27 | + /* Overrides bootstrap's' stylesheet: don't show URLs when printing */ |
| 28 | + a[href]:after { |
| 29 | + content: none; |
| 30 | + } |
| 31 | + |
| 32 | + td.na { |
| 33 | + background: #EEE; |
| 34 | + } |
24 | 35 | } |
25 | 36 | </style> |
26 | 37 |
|
|
32 | 43 | </head> |
33 | 44 | <body role="document"> |
34 | 45 |
|
35 | | -<a href="https://github.com/remram44/regex-cheatsheet"><img style="position: absolute; top: 0; right: 0; border: 0;" src="https://camo.githubusercontent.com/38ef81f8aca64bb9a64448d0d70f1308ef5341ab/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f6461726b626c75655f3132313632312e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png"></a> |
| 46 | +<div class="hidden-print"> |
| 47 | + <a href="https://github.com/remram44/regex-cheatsheet"><img style="position: absolute; top: 0; right: 0; border: 0;" src="https://camo.githubusercontent.com/38ef81f8aca64bb9a64448d0d70f1308ef5341ab/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f6461726b626c75655f3132313632312e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png"></a> |
| 48 | +</div> |
36 | 49 |
|
37 | 50 | <div class="container" role="main"> |
38 | 51 |
|
39 | | -<h1>Regex cheatsheet</h1> |
40 | | - |
41 | | -<p>Many programs use regular expression to find & replace text. However, they tend to come with their own different flavor.</p> |
42 | | - |
43 | | -<p>You can probably expect most modern software and programming languages to be using some variation of the Perl flavor, "PCRE"; however command-line tools (grep, less, ...) will often use the POSIX flavor (sometimes with an extended variant, e.g. <code>egrep</code> or <code>sed -r</code>). ViM also comes with its own syntax (a superset of what Vi accepts).</p> |
44 | | - |
45 | | -<p>This cheatsheet lists the respective <a href="#syntax">syntax of each flavor</a>, and the <a href="#programs">software that uses it</a>.</p> |
| 52 | +<div class="hidden-print"> |
| 53 | + <h1>Regex cheatsheet</h1> |
46 | 54 |
|
47 | | -<p>If you spot errors or missing data, or just want to make this prettier/more accurate, don't hesitate to open an <a href="https://github.com/remram44/regex-cheatsheet/issues/new">issue</a> or a <a href="https://github.com/remram44/regex-cheatsheet/compare/">pull request</a>.</p> |
| 55 | + <p>Many programs use regular expression to find & replace text. However, they tend to come with their own different flavor.</p> |
| 56 | + <p>You can probably expect most modern software and programming languages to be using some variation of the Perl flavor, "PCRE"; however command-line tools (grep, less, ...) will often use the POSIX flavor (sometimes with an extended variant, e.g. <code>egrep</code> or <code>sed -r</code>). ViM also comes with its own syntax (a superset of what Vi accepts).</p> |
| 57 | + <p>This cheatsheet lists the respective <a href="#syntax">syntax of each flavor</a>, and the <a href="#programs">software that uses it</a>.</p> |
| 58 | + <p>If you spot errors or missing data, or just want to make this prettier/more accurate, don't hesitate to open an <a href="https://github.com/remram44/regex-cheatsheet/issues/new">issue</a> or a <a href="https://github.com/remram44/regex-cheatsheet/compare/">pull request</a>.</p> |
| 59 | +</div> |
48 | 60 |
|
49 | 61 | <h1 id="syntax">Syntax</h1> |
50 | 62 |
|
|
0 commit comments