summary refs log tree commit diff
path: root/bin/man1 (follow)
Commit message (Collapse)AuthorAge
* Revert "Add git-import"June McEnroe2023-09-11
| | | | | | This reverts commit 90fefcaa0b70af49061d648ae3566d65abfc2ab0. Moved to jorts.
* Add git-importJune McEnroe2023-09-11
|
* Add when - to print all named datesJune McEnroe2022-09-19
|
* Load dates from ~/.config/when/datesJune McEnroe2022-08-15
|
* Allow names with prefixes of months and daysJune McEnroe2022-08-15
|
* Add named dates to whenJune McEnroe2022-08-15
|
* Add -w to upJune McEnroe2022-07-26
|
* Do basic match highlightingJune McEnroe2022-06-02
|
* Add initial working version of qfJune McEnroe2022-06-02
|
* Add encJune McEnroe2022-01-30
|
* Add LWN to supJune McEnroe2022-01-12
|
* Add tildegit (gitea) to supJune McEnroe2022-01-09
|
* Revert "Add shotty -t to animate (crudely) between snapshots"June McEnroe2021-10-18
| | | | | | | | This reverts commit e52b86b69b9dc6a7b7ec9d578c20d88fc1ccb330. It's mostly irrelevant to how shotty actually functions so I think it would be better done externally. Reverting just to keep the dumb JavaScript in history.
* Add shotty -t to animate (crudely) between snapshotsJune McEnroe2021-10-18
|
* Add ptee -t to output media copy at an intervalJune McEnroe2021-10-18
|
* Swap functions of ^Q and ^S in pteeJune McEnroe2021-10-18
|
* Add shotty -i to output inline colorsJune McEnroe2021-10-18
|
* Cite ctlseqs.ms and UTF-8June McEnroe2021-10-18
|
* Add htagml -m to rename main tagJune McEnroe2021-10-01
|
* Add quickJune McEnroe2021-09-23
|
* Remove Linux-specific utilitiesJune McEnroe2021-09-22
| | | | I haven't used these in ages.
* Rewrite pngo, add explicit optionsJune McEnroe2021-09-21
| | | | Interesting to see how my code habits have changed.
* Remove typer, add downgrade to READMEJune McEnroe2021-09-15
|
* Set bot mode on downgradeJune McEnroe2021-09-15
|
* Add downgrade IRC botJune McEnroe2021-09-14
|
* Add git comment --pretty optionJune McEnroe2021-09-10
|
* Up default min-repeat to 30 linesJune McEnroe2021-09-08
|
* Document and install git-commentJune McEnroe2021-09-08
|
* Document lack of alt text in dehtmlJune McEnroe2021-09-07
| | | | I want to implement this but it requires more complex lexing.
* Add dehtmlJune McEnroe2021-09-07
|
* Strip typer down to copy or reverse modesJune McEnroe2021-07-09
|
* Add patreon to supJune McEnroe2021-07-05
|
* Use $SHELL -c to run up -c | -t commandsJune McEnroe2021-06-21
| | | | And clean up some other things.
* Add copy mode to typerJune McEnroe2021-04-28
|
* Remove hnelJune McEnroe2021-04-26
| | | | I haven't had a use for it in years.
* Add -R reverse typerJune McEnroe2021-04-18
|
* Add typer -P and -c to connect to pounceJune McEnroe2021-03-23
| | | | Of course, running this full time would really fill up the buffer...
* Add typer botJune McEnroe2021-03-23
| | | | Ok maybe I'm an asshole.
* Add -q flag to everJune McEnroe2021-02-24
|
* Add asciinema to supJune McEnroe2021-02-21
|
* Add Liberapay to supJune McEnroe2021-02-21
| | | | | Don't actually need to set a password for this one, but I can automate using the email link to log in.
* Add bugzilla support to supJune McEnroe2021-02-17
|
* Add tildenews support to supJune McEnroe2021-02-16
| | | | See those variables paid off :)
* Add sup for setting single-use passwordsJune McEnroe2021-02-16
|
* Add missing %U for RFCs in bibsortJune McEnroe2021-02-16
|
* Use flags for pbd client behaviourJune McEnroe2021-02-09
|
* Use scrot for up -s if no screencaptureJune McEnroe2021-02-07
| | | | Still missing putting the URL in an X selection.
* Add xterm output to schemeJune McEnroe2021-02-06
|
* Generate tags for sh files in mtagsJune McEnroe2021-01-20
| | | | | Only matches functions declared at the beginnings of lines, but I'm fine with that.
* Add messy sh lexerJune McEnroe2021-01-20
| | | | Surprisingly seems to work for everything I looked at in my repos.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-11-15 04:13:50 +0000
td>Jason Bowen I've attached a patch which adds the subdir-objects option to AM_INIT_AUTOMAKE. For a while now when I've compiled dash I received a warning from automake that there are source files in a subdirectory but that the subdir-objects automake option was not supplied. I've just been adding it myself, but I finally got around to submitting a patch. The code still compiles for now (i'm using automake 1.15.1), but warning text is rarely nice to see and, if the warning text is to be believed, then the warning will eventually become an error. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19eval: Restore input files in evalcommandHerbert Xu When evalcommand invokes a command that modifies parsefile and then bails out without popping the file, we need to ensure the input file is restored so that the shell can continue to execute. Reported-by: Martijn Dekker <martijn@inlv.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19eval: Reap zombies after built-in commands and functionsHerbert Xu Currently dash does not reap dead children after built-in commands or functions. This means that if you construct a loop consisting of solely built-in commands and functions, then zombies can hang around indefinitely. This patch fixes this by reaping when necessary after each built-in command and function. Reported-by: Denys Vlasenko <vda.linux@googlemail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19redir: Fix typo in noclobber codeHerbert Xu The noclobber code has a typo in it that causes it to fail. This patch fixes it. Reported-by: Denys Vlasenko <vda.linux@googlemail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19expand: 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