aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update the READMEHEADmasterThomas Voss 2024-09-231-19/+1
|
* Add a dist target for cross-compilationThomas Voss 2024-05-282-0/+12
|
* Update READMEThomas Voss 2024-05-281-2/+12
|
* Run go mod tidyThomas Voss 2024-05-282-5/+1
|
* Add support for commentsv3.1.0Thomas Voss 2024-04-184-3/+52
|
* Document the --no-doctype long-optionThomas Voss 2024-04-181-2/+2
|
* Switch to opts for option parsingThomas Voss 2024-04-183-11/+21
|
* Remove the ‘>’ prefixv3.0.0Thomas Voss 2023-11-015-55/+66
| | | | | | The rationale was explained on the mailing list[1]. [1]: https://paste.thomasvoss.com/353
* Minor refactorThomas Voss 2023-11-011-3/+3
|
* Update READMEThomas Voss 2023-10-291-2/+37
|
* Fix typov2.0.1Thomas Voss 2023-10-281-1/+1
|
* Allow for true HTML ID- and class shorthandsv2.0.0Thomas Voss 2023-10-284-8/+50
|
* Rename some testsThomas Voss 2023-10-211-3/+3
|
* Run ‘go fmt’Thomas Voss 2023-10-212-3/+4
|
* Add a few tests for the parserThomas Voss 2023-10-211-0/+62
|
* Comment parser.goThomas Voss 2023-10-211-2/+20
|
* Add tests for the formatterThomas Voss 2023-10-211-0/+258
|
* Escape runes in class namesThomas Voss 2023-10-211-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.goThomas Voss 2023-10-201-0/+178
|
* Document reader.goThomas Voss 2023-10-201-0/+18
|
* Improve the implementation of peekRune()Thomas Voss 2023-10-201-17/+12
|
* Make use of the ‘./...’ wildcardThomas Voss 2023-10-201-1/+1
|
* Add a target to run testsThomas Voss 2023-10-201-0/+3
|
* Mark Makefile as being POSIX compliantThomas Voss 2023-10-201-0/+2
|
* Fix printing classes and attrsv1.0.2jturtle 2023-10-201-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-loopThomas Voss 2023-10-101-9/+10
|
* Detail how to have empty non-void tagsv1.0.1Thomas Voss 2023-10-021-1/+10
|
* Remove whitespaceThomas Voss 2023-10-021-2/+0
|
* Fix class/attribute mixup bugjturtle 2023-10-021-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.0Thomas Voss 2023-09-111-1/+1
| | | | I forgot to update the date last time I changed this.
* Minor refactoringThomas Voss 2023-09-111-15/+10
|
* Correct errors in READMEThomas Voss 2023-09-111-4/+4
|
* Run ‘go fmt’Thomas Voss 2023-09-111-9/+9
|
* Add the ‘=’ node for whitespace trimmingThomas Voss 2023-09-113-53/+38
|
* Wrap example code to 73 columnsThomas Voss 2023-09-111-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 exampleThomas Voss 2023-09-111-4/+7
|
* Add the ‘>’ node modifierThomas Voss 2023-09-113-29/+65
|
* Specify constant typeThomas Voss 2023-09-111-1/+1
|
* Fix a panicThomas Voss 2023-09-101-1/+1
|
* Remove useless escapesThomas Voss 2023-09-101-3/+3
|
* Support multiple root-level nodesThomas Voss 2023-09-101-10/+19
|
* Add a ‘Documentation’ section to the READMEThomas Voss 2023-09-101-0/+5
|
* Remove all XML supportThomas Voss 2023-09-106-150/+42
|
* Add the ‘-x’ command-line optionThomas Voss 2023-09-104-3/+26
|
* Rework some of the formatting- and parsing codeThomas Voss 2023-09-103-86/+95
|
* Write the initial gsp(5) manualThomas Voss 2023-09-101-1/+267
|
* Bump dateThomas Voss 2023-09-101-1/+1
|
* Mention XML in the READMEThomas Voss 2023-09-101-0/+5
|
* Update manual with XML informationThomas Voss 2023-09-101-4/+13
|
* Add a skeleton for an initial gsp(5)Thomas Voss 2023-09-091-0/+11
|