Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add a dist target for cross-compilation | Thomas Voss | 2024-05-28 | 2 | -0/+12 |
| | |||||
* | Update README | Thomas Voss | 2024-05-28 | 1 | -2/+12 |
| | |||||
* | Run go mod tidy | Thomas Voss | 2024-05-28 | 2 | -5/+1 |
| | |||||
* | Add support for commentsv3.1.0 | Thomas Voss | 2024-04-18 | 4 | -3/+52 |
| | |||||
* | Document the --no-doctype long-option | Thomas Voss | 2024-04-18 | 1 | -2/+2 |
| | |||||
* | Switch to opts for option parsing | Thomas Voss | 2024-04-18 | 3 | -11/+21 |
| | |||||
* | Remove the ‘>’ prefixv3.0.0 | Thomas Voss | 2023-11-01 | 5 | -55/+66 |
| | | | | | | The rationale was explained on the mailing list[1]. [1]: https://paste.thomasvoss.com/353 | ||||
* | Minor refactor | Thomas Voss | 2023-11-01 | 1 | -3/+3 |
| | |||||
* | Update README | Thomas Voss | 2023-10-29 | 1 | -2/+37 |
| | |||||
* | Fix typov2.0.1 | Thomas Voss | 2023-10-28 | 1 | -1/+1 |
| | |||||
* | Allow for true HTML ID- and class shorthandsv2.0.0 | Thomas Voss | 2023-10-28 | 4 | -8/+50 |
| | |||||
* | Rename some tests | Thomas Voss | 2023-10-21 | 1 | -3/+3 |
| | |||||
* | Run ‘go fmt’ | Thomas Voss | 2023-10-21 | 2 | -3/+4 |
| | |||||
* | Add a few tests for the parser | Thomas Voss | 2023-10-21 | 1 | -0/+62 |
| | |||||
* | Comment parser.go | Thomas Voss | 2023-10-21 | 1 | -2/+20 |
| | |||||
* | Add tests for the formatter | Thomas Voss | 2023-10-21 | 1 | -0/+258 |
| | |||||
* | Escape runes in class names | Thomas Voss | 2023-10-21 | 1 | -8/+12 |
| | | | | | | I cannot think of a single situation where you’d ever end up in this situation, and I also am not even sure if it’s even meant to be legal HTML. Better to be on the safe side I guess. | ||||
* | Add tests for reader.go | Thomas Voss | 2023-10-20 | 1 | -0/+178 |
| | |||||
* | Document reader.go | Thomas Voss | 2023-10-20 | 1 | -0/+18 |
| | |||||
* | Improve the implementation of peekRune() | Thomas Voss | 2023-10-20 | 1 | -17/+12 |
| | |||||
* | Make use of the ‘./...’ wildcard | Thomas Voss | 2023-10-20 | 1 | -1/+1 |
| | |||||
* | Add a target to run tests | Thomas Voss | 2023-10-20 | 1 | -0/+3 |
| | |||||
* | Mark Makefile as being POSIX compliant | Thomas Voss | 2023-10-20 | 1 | -0/+2 |
| | |||||
* | Fix printing classes and attrsv1.0.2 | jturtle | 2023-10-20 | 1 | -1/+1 |
| | | | | | | | | | Well well well, here we are again. Iterate over the `nClasses` list instead of every attr after printing the classes. With all due respect, you should consider writing a test suite to catch silly errors like this. | ||||
* | Don’t use lambdas, and just use a damn for-loop | Thomas Voss | 2023-10-10 | 1 | -9/+10 |
| | |||||
* | Detail how to have empty non-void tagsv1.0.1 | Thomas Voss | 2023-10-02 | 1 | -1/+10 |
| | |||||
* | Remove whitespace | Thomas Voss | 2023-10-02 | 1 | -2/+0 |
| | |||||
* | Fix class/attribute mixup bug | jturtle | 2023-10-02 | 1 | -1/+4 |
| | | | | | | | | | | | | | | | | | | There's a bug in the current version of GSP where an element like this: p .class attribute="value" {-} would be transpiled as this: <p class="value" attribute="value"></p> The `classes` slice in `func printAttrs` (`formatter.go`, line 50) was the cause. I fixed it by making a deep copy of the `attrs` slice. I'm not a Go programmer, there might be a nicer way to make a deep copy of a slice. But it does, indeed, work. P.S. thanks for making this, writing HTML by hand is now slightly less painful! | ||||
* | Bump manual datev1.0.0 | Thomas Voss | 2023-09-11 | 1 | -1/+1 |
| | | | | I forgot to update the date last time I changed this. | ||||
* | Minor refactoring | Thomas Voss | 2023-09-11 | 1 | -15/+10 |
| | |||||
* | Correct errors in README | Thomas Voss | 2023-09-11 | 1 | -4/+4 |
| | |||||
* | Run ‘go fmt’ | Thomas Voss | 2023-09-11 | 1 | -9/+9 |
| | |||||
* | Add the ‘=’ node for whitespace trimming | Thomas Voss | 2023-09-11 | 3 | -53/+38 |
| | |||||
* | Wrap example code to 73 columns | Thomas Voss | 2023-09-11 | 1 | -8/+9 |
| | | | | | | Normally I wrap code and stuff to 80 columns, but I’m going to use 73 for the examples in the manuals as manual page readers are probably indenting stuff quite a bit. | ||||
* | Fix invalid markup in example | Thomas Voss | 2023-09-11 | 1 | -4/+7 |
| | |||||
* | Add the ‘>’ node modifier | Thomas Voss | 2023-09-11 | 3 | -29/+65 |
| | |||||
* | Specify constant type | Thomas Voss | 2023-09-11 | 1 | -1/+1 |
| | |||||
* | Fix a panic | Thomas Voss | 2023-09-10 | 1 | -1/+1 |
| | |||||
* | Remove useless escapes | Thomas Voss | 2023-09-10 | 1 | -3/+3 |
| | |||||
* | Support multiple root-level nodes | Thomas Voss | 2023-09-10 | 1 | -10/+19 |
| | |||||
* | Add a ‘Documentation’ section to the README | Thomas Voss | 2023-09-10 | 1 | -0/+5 |
| | |||||
* | Remove all XML support | Thomas Voss | 2023-09-10 | 6 | -150/+42 |
| | |||||
* | Add the ‘-x’ command-line option | Thomas Voss | 2023-09-10 | 4 | -3/+26 |
| | |||||
* | Rework some of the formatting- and parsing code | Thomas Voss | 2023-09-10 | 3 | -86/+95 |
| | |||||
* | Write the initial gsp(5) manual | Thomas Voss | 2023-09-10 | 1 | -1/+267 |
| | |||||
* | Bump date | Thomas Voss | 2023-09-10 | 1 | -1/+1 |
| | |||||
* | Mention XML in the README | Thomas Voss | 2023-09-10 | 1 | -0/+5 |
| | |||||
* | Update manual with XML information | Thomas Voss | 2023-09-10 | 1 | -4/+13 |
| | |||||
* | Add a skeleton for an initial gsp(5) | Thomas Voss | 2023-09-09 | 1 | -0/+11 |
| | |||||
* | Install gsp(5) manual | Thomas Voss | 2023-09-09 | 1 | -1/+4 |
| |