diff options
Diffstat (limited to 'src/blog/grab/index.gsp')
| -rw-r--r-- | src/blog/grab/index.gsp | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/src/blog/grab/index.gsp b/src/blog/grab/index.gsp index 87ebb5f..38918eb 100644 --- a/src/blog/grab/index.gsp +++ b/src/blog/grab/index.gsp @@ -125,7 +125,7 @@ html lang="en" { p {- So over the following few days I made major changes, rewrote lots of the - code, and overall turned my tool — @code{-grab} — into a staple part of + code, and overall turned my tool – @code{-grab} – into a staple part of my hackers toolbelt. } @@ -134,8 +134,8 @@ html lang="en" { If you’re familiar with the UNIX environment, you’re probably used to querying text with tools such as @code{-sed} and @code{-awk} using regular expressions. These are the same regular expressions we as - programmers all know and love, but with one important — yet often - overlooked — characteristic: you cannot match the newline. + programmers all know and love, but with one important – yet often + overlooked – characteristic: you cannot match the newline. } p {- @@ -143,8 +143,8 @@ html lang="en" { newline is treated no differently from another other character you want to match. Want to match an entire paragraph of text? The pattern is as simple as ‘@code{-[^\\n].+?(?=\\n\\n|$)}’. It may look - complicated if you’re new to regular expressions — PCREs to be specific - — but it’s really quite simple. You just match a non-newline character, + complicated if you’re new to regular expressions – PCREs to be specific + – but it’s really quite simple. You just match a non-newline character, and then as many characters as possible until reaching either a double newline, or the end of input. } @@ -272,4 +272,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file |