summary refs log tree commit diff
path: root/etc (follow)
Commit message (Collapse)AuthorAge
...
* Run tf/cfg link script with /bin/shJune McEnroe2018-08-18
|
* Add gitea2mastodon CGI scriptJune McEnroe2018-08-17
| | | | If you're seeing this on Mastodon, it works.
* Disable visual bell entirely in TerminalJune McEnroe2018-08-16
| | | | You can't turn off bell in ksh.
* Move heavyweapons binds to autoexecJune McEnroe2018-06-10
|
* Add explode bindJune McEnroe2018-06-09
|
* Remove scout configJune McEnroe2018-06-09
|
* Remove viewmodel disablingJune McEnroe2018-05-30
| | | | | Switched to minimized viewmodels with lowest viewmodel FOV and it's much better.
* Remove demoman mouse2 bindJune McEnroe2018-05-30
| | | | I started playing with the sticky jumper rather than a shield.
* Use scheme for Light terminalJune McEnroe2018-05-29
| | | | All I did was swap black and white. Sitting outside now. Looks fine.
* Set TERM=xterm in Terminal.appJune McEnroe2018-05-13
| | | | 16 colours is all I need.
* Tabify shell scriptsJune McEnroe2018-05-13
|
* Add demoman configJune McEnroe2018-04-22
| | | | Haven't tested it yet but should be good for hybrid knight.
* Add TF2 configsJune McEnroe2018-04-15
|
* Output Linux console escapes from schemeJune McEnroe2018-03-31
|
* Brighten color schemeJune McEnroe2018-03-31
|
* Set Dark terminal to schemeJune McEnroe2018-03-31
|
* Set Light terminal white to Gruvbox fg3June McEnroe2018-02-28
|
* Switch to and vendor Go Mono fontJune McEnroe2018-02-21
| | | | | | | Go Mono is almost identical to Luxi Mono (same designers) but MIT-licensed. From https://go.googlesource.com/image font/gofont/ttfs.
* Remove Tarmak and Colemak keylayoutsJune McEnroe2018-01-30
|
* Switch back to QWERTY on LinuxJune McEnroe2018-01-29
| | | | | I think the only thing I'll miss is N and E on home row (which was Tarmak 1, if I remember correctly).
* Fix CodeQWERTY layoutJune McEnroe2018-01-27
| | | | | | Based on the Canadian layout file from Ukelele with the same modifications I've been making to the Tarmak layouts so that control and command use the default layout.
* Add CodeQWERTY keylayoutJune McEnroe2018-01-27
| | | | | Yeah, I think it's time to switch back. My typing seems still worse than it started, and keeping weird layouts is inconvenient.
* Convert to CodeColemak keylayoutJune McEnroe2018-01-26
|
* Add Colemak keylayoutJune McEnroe2018-01-26
|
* Remove Code Tarmak 3June McEnroe2017-12-31
|
* Update Linux console map to Tarmak 4June McEnroe2017-09-27
|
* Add Code Tarmak 4 layoutJune McEnroe2017-09-27
| | | | So close now!
* Rename files directory etcJune McEnroe2017-09-15
|
* Remove unused configsJune McEnroe2013-10-14
|
* Update system configurationsJune McEnroe2013-04-24
|
* Add PulseAudio configurationJune McEnroe2012-12-19
|
* Remove rc.confJune McEnroe2012-12-19
|
* Add cpupower configurationJune McEnroe2012-10-06
|
* Add system-wide configuration filesJune McEnroe2012-10-06
generated by cgit-pink 1.4.1 (git 2.36.1) at 2025-02-18 09:17:21 +0000
rrectly 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