summary refs log tree commit diff
path: root/www (follow)
Commit message (Collapse)AuthorAge
* Add some missing justification to "C Style"June McEnroe2021-03-16
|
* Publish "C Style"June McEnroe2021-03-16
|
* Add bubger to causal.agency pageJune McEnroe2021-03-14
|
* Publish "Mailing List"June McEnroe2021-03-04
|
* Add mailist, liberapay to indexJune McEnroe2021-02-24
|
* Publish "Operating systems"June McEnroe2021-02-22
|
* Iterate over text files to generate feedJune McEnroe2021-02-22
| | | | So that only "published" text files are included.
* Publish "Unpasswords"June McEnroe2021-02-20
|
* Add xdimmer to "Using OpenBSD"June McEnroe2021-02-15
|
* Publish "Using OpenBSD"June McEnroe2021-02-14
|
* Use owner-filter to add Liberapay donation buttonsJune McEnroe2021-02-04
|
* Use owner-filter for repo page headersJune McEnroe2021-02-04
| | | | Previously it was only used if owners were displayed on the index.
* Remove cgit logo using cgitrcJune McEnroe2021-02-04
| | | | | It's not documented that you can set logo to empty string to remove it, I just noticed by reading print_header.
* Use mtags for sh in source-filterJune McEnroe2021-01-20
|
* Add all target to git.causal.agency MakefileJune McEnroe2021-01-20
|
* Remove Lua supportJune McEnroe2021-01-20
| | | | | Lua support is unused and the dlsym fwrite/write hacks horrify me. Clean it up.
* Fix tests for diff spansJune McEnroe2021-01-20
|
* Use mtags in source-filterJune McEnroe2021-01-20
|
* Publish "reusing tags"June McEnroe2021-01-17
|
* Use <pre> and <span> to print diffsJune McEnroe2021-01-17
| | | | | | | This correctly preserves whitespace in browsers without CSS, as an alternative to [1]. [1]: https://80x24.org/cgit.git/commit/?id=7c692e6137697de8a8473c4de5c3de4fb03a2989
* Ignore cgit/gitJune McEnroe2021-01-17
|
* Link to causal.agency cgit from footerJune McEnroe2021-01-17
|
* Use buffered stdioEric Wong2021-01-17
| | | | | | | | | | | | | | | | | | | | | | | Our generation of HTML triggers many small write(2) syscalls which is inefficient. Time output on a horrible query against my git.git mirror shows significant performance improvement: QUERY_STRING='id=2b93bfac0f5bcabbf60f174f4e7bfa9e318e64d5&id2=d6da71a9d16b8cf27f9d8f90692d3625c849cbc8' PATH_INFO=/mirrors/git.git/diff export QUERY_STRING PATH_INFO time ./cgit >/dev/null Before: real 0m1.585s user 0m0.904s sys 0m0.658s After: real 0m0.750s user 0m0.666s sys 0m0.076s
* Remove redundant title on repo anchorsChris Mayo2021-01-17
| | | | | | | The title attribute was being set to the same value as the anchor element text. Signed-off-by: Chris Mayo <aklhfex@gmail.com>
* Improve button spacing for browsers w/o CSSEric Wong2021-01-17
| | | | | | | For browsers on low-end machines running browsers without CSS support, the default tree view displayed "logplain" when it should be "log plain". Stop relying on CSS and add a space in between elements to improve accessibility.
* Improve decoration display for browsers without CSSEric Wong2021-01-17
| | | | | | Text-based browsers without CSS support show all the decorations bunched together without spacing. Rely on a whitespace instead of CSS support.
* Use <pre> for commit-msgEric Wong2021-01-17
| | | | | This preserves formatting readable for users of text-based browsers without CSS support.
* Improve pageheader display on text-based browsersEric Wong2021-01-17
| | | | | | | | | | | Text-based browsers (and some GUI browsers such as dillo) display the pageheader as: "summaryrefslogtreecommitdiff" This is difficult-to-read. Improve accessibility for users who cannot run memory-hungry browsers by using whitespace instead of relying on CSS.
* Use git raw note formatChris Mayo2021-01-17
| | | | | | | | | | | | | | | | Currently a commit note is shown as: Notes Notes: <note text> Change to: Notes <note text> Signed-off-by: Chris Mayo <aklhfex at gmail.com>
* Touch tags in source-filterJune McEnroe2021-01-17
| | | | | ctags does not create the tags file if the input file contains nothing worth tagging, and htagml errors if there is no tags file to load.
* Use a temp directory in source-filter to preserve nameJune McEnroe2021-01-15
| | | | Otherwise ctags can't figure out if the input is a lex or yacc file.
* Call cap_rights_limit on stderr tooJune McEnroe2021-01-14
|
* Add link to gopher version of text.causal.agencyJune McEnroe2021-01-14
|
* Add igp gopher server for text.causal.agencyJune McEnroe2021-01-14
|
* Switch git.causal.agency to hilex and htagmlJune McEnroe2021-01-13
| | | | Still missing a shell lexer in hilex, but well... it's shell.
* Style causal.agency like bin HTMLJune McEnroe2021-01-12
|
* Replace causal.agency with a simple mdoc pageJune McEnroe2021-01-12
|
* Publish "Using vi"June McEnroe2021-01-11
|
* Update taglineJune McEnroe2021-01-05
|
* Add "this commit" option to switch formAlyssa Ross2020-12-27
| | | | | | | | | | | | | | | | | Branches are grouped into their own section to make the "this commit" option visually distinct. Adding this option will result in two options being marked as selected if a branch has the same name as a commit oid. But that would cause all sorts of other problems anyway (attempting to switch to the branch would actually give you the commit, etc.), so let's not worry about that. A "permalink" link on the blob view next to the "plain" link would probably be more discoverable, but that would only work for the blob view. The switch UI is visible everywhere. Signed-off-by: Alyssa Ross <hi@alyssa.is>
* Show subject in commit page titleJune McEnroe2020-12-27
|
* Show symlink targets in tree listingJune McEnroe2020-12-27
| | | | | Add links to symbolic link targets in tree listings, formatted like "ls -l". Path normalization collapses any ".." components of the link.
* Disallow blame in robots.txtJune McEnroe2020-12-27
|
* Don't link to blame for binary blobsJune McEnroe2020-12-27
|
* Bail from blame if blob is binaryJune McEnroe2020-12-27
| | | | This avoids piping binary blobs through the source-filter.
* Remove dependency on memrchrJune McEnroe2020-12-27
|
* Remove cgit/git submoduleJune McEnroe2020-12-27
|
* Merge commit '85016e706cd00e527dba3fa83b2783dfb56a4ffa' as ↵June McEnroe2020-12-27
| | | | | | 'www/git.causal.agency/cgit' From tag 'v1.2.3'.
* Note lack of macro expansions in Q(...)June McEnroe2020-12-03
|
* Fix missing "to" in "hot tips"June McEnroe2020-12-02
|
mpty 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