summary refs log tree commit diff
path: root/bin (follow)
Commit message (Collapse)AuthorAge
...
* Avoid matching tag text inside HTML elementsJune McEnroe2021-01-12
|
* Use hilex for up -hJune McEnroe2021-01-12
|
* Use hilex for bin HTMLJune McEnroe2021-01-12
|
* Don't output a pre in hilex by defaultJune McEnroe2021-01-12
|
* Move hilex out of hilex directoryJune McEnroe2021-01-12
|
* Consolidate hilex formatters into hilex.cJune McEnroe2021-01-12
|
* Remove hacky tagging from hilexJune McEnroe2021-01-12
| | | | God that makes the lexers so much simpler.
* Add htagml -iJune McEnroe2021-01-12
|
* Render tag index in HTMLJune McEnroe2021-01-12
|
* Add htagml -xJune McEnroe2021-01-12
|
* Prevent matching the same tag twiceJune McEnroe2021-01-12
|
* Process htagml file line by lineJune McEnroe2021-01-12
| | | | | | This simplifies some things, adds support for line number tag definitions, and should enable combining htagml with other preprocessors in the future.
* Split fields by tab onlyJune McEnroe2021-01-12
| | | | Also don't fail hard on non-forward-search definitions.
* List both Makefile and html.sh under README.7June McEnroe2021-01-12
|
* Add htagml exampleJune McEnroe2021-01-12
|
* Use mandoc and htagml for bin htmlJune McEnroe2021-01-12
|
* Add htagmlJune McEnroe2021-01-12
|
* Add c -t flag to print expression typeJune McEnroe2021-01-09
| | | | Also add missing float case.
* Clean up make lexerJune McEnroe2021-01-02
| | | | Still feels pretty messy though.
* Tag top-level typedefs the same way as function definitionsJune McEnroe2021-01-02
|
* Clean up order lexerJune McEnroe2021-01-01
|
* Remove empty comma statement from bitJune McEnroe2021-01-01
|
* Add ASCII control code names to bitJune McEnroe2020-12-31
|
* Simplify bit lexing and parsingJune McEnroe2020-12-31
| | | | Also print the value of each expression separated by commas.
* Print octal for 8 bits in bitJune McEnroe2020-12-30
|
* Add unary & to bitJune McEnroe2020-12-30
| | | | Also unary + and fix precedence of unary -.
* Support unary + in orderJune McEnroe2020-12-30
| | | | Missed this because operator(7) just doesn't list it, oddly.
* Add postfix $ operator to bitJune McEnroe2020-12-30
|
* Add make lexerJune McEnroe2020-12-29
| | | | | This is kind of a mess and needs to be cleaned up against more careful reading of the make grammar.
* Clean up C lexerJune McEnroe2020-12-29
| | | | This ordering of rules feels much cleaner.
* Clean up hilex code somewhatJune McEnroe2020-12-29
|
* Match lex/yacc %% %{ %} lines as MacroJune McEnroe2020-12-29
|
* Match top-level C definitions as IdentifierTagJune McEnroe2020-12-29
|
* Match C type declarations as IdentifierTagJune McEnroe2020-12-29
|
* Match function-like macro definitions as IdentifierTagJune McEnroe2020-12-29
|
* Reconfigure C macro start conditionsJune McEnroe2020-12-29
|
* Document HTML class namesJune McEnroe2020-12-29
|
* Rename Tag class to IdentifierTagJune McEnroe2020-12-29
|
* Change HTML class from hi to hilexJune McEnroe2020-12-29
| | | | You can tell I was just copying the HTML code huh.
* Add hilex HTML outputJune McEnroe2020-12-29
|
* Add hilex manual pageJune McEnroe2020-12-29
|
* Match Objective-C #import in C lexerJune McEnroe2020-12-29
|
* Add hilex IRC formatterJune McEnroe2020-12-28
|
* Generate Tag tokens for mdoc headingsJune McEnroe2020-12-28
|
* Add mdoc lexerJune McEnroe2020-12-28
|
* Lex strings inside macrosJune McEnroe2020-12-28
|
* Set H_SETUNIQUEJune McEnroe2020-12-28
|
* Add initial version of hilexJune McEnroe2020-12-28
| | | | | | | | | | hilex is meant to replace hi, based on lex rather than a mess of overlapping regexps. I want to preserve hi's tagging abilities, but that will require some amount of parsing/post-processing, which I'm not sure how to approach yet. Macro lexing for C still needs work, as I want to match strings and comments inside macros.
* Remove 1shJune McEnroe2020-12-23
|
* Fix dash Makefile compatibility with BSD makeJune McEnroe2020-12-23
|
979644 bytes with a cache-miss > mricon@nikko:[/tmp]$ wget -O yes-cache > "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=2840c > 566e95599cd60c7143762ca8b49d9395050" ... > 2014-06-11 15:41:46 (1.05 MB/s) - ‘yes-cache’ saved [978944] 978944 (956KB exactly) with a cache-hit Since the "html" functions use raw write(2) to STDIO_FILENO, we don't notice problems with most pages, but raw patches write using printf(3). This is fine if we're outputting straight to stdout since the buffers are flushed on exit, but we close the cache output before this, so the cached output ends up being truncated. Make sure the buffers are flushed when we finish outputting a patch so that we avoid this. No other UIs use printf(3) so we do not need to worry about them. Actually, it's slightly more interesting than this... since we don't set GIT_FLUSH, Git decides whether or not it will flush stdout after writing each commit based on whether or not stdout points to a regular file (in maybe_flush_or_die()). Which means that when writing directly to the webserver, Git flushes stdout for us, but when we redirect stdout to the cache it points to a regular file so Git no longer flushes the output for us. The patch is still correct, but perhaps the full explanation is interesting! Reported-by: Konstantin Ryabitsev <mricon@kernel.org> 2014-06-28ui-log: ignore unhandled argumentsJohn Keeping If you search for a bogus range string here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/ Using something like "range" and "qwerty123456", it returns an "Internal Server Error" and the following in the logs: > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] fatal: > ambiguous argument 'qwerty123456': unknown revision or path not in the > working tree., referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Use '--' to > separate paths from revisions, like this:, referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] 'git <command> > [<revision>...] -- [<file>...]', referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Premature end > of script headers: cgit, referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ The cache will kick in, so if you search for the same string again, it'll show an empty range, so you have to change the bogus strings each time. This is because we just pass the arguments straight to Git's revision parsing machinery which die()s if it cannot parse an argument, printing the above to stderr and exiting. The patch below makes it a bit friendlier by just ignoring unhandled arguments, but I can't see an easy way to report errors when we can't parse revision arguments without losing the flexibility of supporting all of the revision specifiers supported by Git. Reported-by: Konstantin Ryabitsev <mricon@kernel.org> 2014-06-28git: update for git 2.0Christian Hesse prefixcmp() and suffixcmp() have been remove, functionality is now provided by starts_with() and ends_with(). Retrurn values have been changed, so instead of just renaming we have to fix logic. Everything else looks just fine. 2014-04-17remove trailing whitespaces from source filesChristian Hesse 2014-04-12git: update to 1.9.2Christian Hesse Everything works just bumping the version in Makefile and commit hash in submodule. No code changes required. 2014-04-05Fix cgit_parse_url when a repo url is contained in another repo urlJulian Maurice For example, if I have two repos (remove-suffix is enabled): /foo /foo/bar http://cgit/foo/bar/ is interpreted as "repository 'foo', command 'bar'" instead of "repository 'foo/bar'" 2014-03-20Makefile: use more reliable git tarball mirrorJason A. Donenfeld 2014-03-20git: update to 1.9.1Christian Hesse