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
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2025-11-03 15:42:07 +0000
853a8f4689808e0976e&follow=1'>expand: Fix glibc glob(3) supportHerbert Xu It's been a while since we disabled glob(3) support by default. It appears to be working now, however, we have to change our code to detect the no-match case correctly. In particular, we need to test for GLOB_NOMAGIC | GLOB_NOCHECK instead of GLOB_MAGCHAR. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix buffer overflow in expandmetaHerbert Xu The native version of expandmeta allocates a buffer that may be overrun for two reasons. First of all the size is 1 byte too small but this is normally hidden because the minimum size is rounded up to 2048 bytes. Secondly, if the directory level is deep enough, any buffer can be overrun. This patch fixes both problems by calling realloc when necessary. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02builtin: Move echo space/nl handling into print_escape_strHerbert Xu Currently echocmd uses print_escape_str to do everything apart from printing the spaces/newlines separating its arguments. This patch moves the actual printing into print_escape_str as well using the format parameter. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02builtin: Fix echo performance regressionHerbert Xu The commit d6c0e1e2ffbf7913ab69d51cc794d48d41c8fcb1 ("[BUILTIN] Handle embedded NULs correctly in printf") caused a performance regression in the echo built-in because every echo call now goes through the printf %b slow path where the string is always printed twice to ensure the space padding is correct in the presence of NUL characters. In fact this regression applies to printf %b as well. This is easily fixed by making printf %b take the fast path when no precision/field width modifiers are present. This patch also changes the second strchurnul call to strspn which generates slightly better code. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix ghost fields with unquoted $@/$*Herbert Xu Harald van Dijk <harald@gigawatt.nl> wrote: > On 22/03/2018 22:38, Martijn Dekker wrote: >> Op 22-03-18 om 20:28 schreef Harald van Dijk: >>> On 22/03/2018 03:40, Martijn Dekker wrote: >>>> This patch fixes the bug that, given no positional parameters, unquoted >>>> $@ and $* incorrectly generate one empty field (they should generate no >>>> fields). Apparently that was a side effect of the above. >>> >>> This seems weird though. If you want to remove the recording of empty >>> regions because they are pointless, then how does removing them fix a >>> bug? Doesn't this show that empty regions do have an effect? Perhaps >>> they're not supposed to have any effect, perhaps it's a specific >>> combination of empty regions and something else that triggers some bug, >>> and perhaps that combination can no longer occur with your patch. >> >> The latter is my guess, but I haven't had time to investigate it. > > Looking into it again: > > When IFS is set to an empty string, sepc is set to '\0' in varvalue(). > This then causes *quotedp to be set to true, meaning evalvar()'s quoted > variable is turned on. quoted is then passed to recordregion() as the > nulonly parameter. > > ifsp->nulonly has a bigger effect than merely selecting whether to use > $IFS or whether to only split on null bytes: in ifsbreakup(), nulonly > also causes string termination to be suppressed. That's correct: that > special treatment is required to preserve empty fields in "$@" > expansion. But it should *only* be used when $@ is quoted: ifsbreakup() > takes nulonly from the last IFS region, even if it's empty, so having an > additional zero-length region with nulonly enabled causes confusion. > > Passing quoted by value to varvalue() and not attempting to modify it > should therefore, and in my quick testing does, also work to fix the > original $@ bug. You're right. The proper fix to this is to ensure that nulonly is not set in varvalue for $*. It should only be set for $@ when it's inside double quotes. In fact there is another bug while we're playing with $@/$*. When IFS is set to a non-whitespace character such as :, $* outside quotes won't remove empty fields as it should. This patch fixes both problems. Reported-by: Martijn Dekker <martijn@inlv.org> Suggested-by: Harald van Dijk <harald@gigawatt.nl> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02parser: Allow newlines within parameter substitutionHerbert Xu On Fri, Mar 16, 2018 at 11:27:22AM +0800, Herbert Xu wrote: > On Thu, Mar 15, 2018 at 10:49:15PM +0100, Harald van Dijk wrote: > > > > Okay, it can be trivially modified to something that does work in other > > shells (even if it were actually executed), but gets rejected at parse time > > by dash: > > > > if false; then > > : ${$+ > > } > > fi > > That's just a bug in dash's parser with ${} in general, because > it bombs out without the if clause too: > > : ${$+ > } This patch fixes the parsing of newlines with parameter substitution. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix bugs with words connected to the right of $@Herbert Xu On Sun, Mar 04, 2018 at 12:44:59PM +0100, Harald van Dijk wrote: > > command: set -- a ""; space=" "; printf "<%s>" "$@"$space > bash: <a><> > dash 0.5.8: <a>< > > dash 0.5.9.1: <a>< > > dash patched: <a><> This is actually composed of two bugs. First of all our tracking of quotemark is wrong so anything after "$@" becomes quoted. Once we fix that then the problem is that the first space character after "$@" is not recognised as an IFS. This patch fixes both. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-25Revert "[BUILTIN] Remove unnecessary restoration of format string in printf"Herbert Xu This reverts commit 7bb413255368e94395237d789f522891093c5774. The commit breaks printf with more than argument. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-22parser: Fix backquote support in here-document EOF markHerbert Xu