~nprescott

Recent activity

[PATCH sr.ht-docs] add links to hg.sr.ht graphql api 2 months ago

From Nolan Prescott to ~sircmpwn/sr.ht-dev

additionally fix typo-reference to builds.sr.ht

diff --git a/graphql.md b/graphql.md
--- a/graphql.md
+++ b/graphql.md
@@ -33,6 +33,7 @@ queries you perform will affect your rea

- [builds.sr.ht playground](https://builds.sr.ht/graphql)
- [git.sr.ht playground](https://git.sr.ht/graphql)
- [hg.sr.ht playground](https://hg.sr.ht/graphql)
- [meta.sr.ht playground](https://meta.sr.ht/graphql)
- [todo.sr.ht playground](https://todo.sr.ht/graphql)
- [lists.sr.ht playground](https://lists.sr.ht/graphql)
diff --git a/hg.sr.ht/graphql.md b/hg.sr.ht/graphql.md
[message trimmed]

[PATCH gamja v2] sort member-list with localeCompare 2 months ago

From Nolan Prescott to ~emersion/public-inbox

The difference in case sensitivity is the most obvious change with
servers like soju that support CASEMAPPING ascii and
rfc1459. Currently the list:
  'Alpha', 'aardvark', 'Charlie', 'comma'
currently sorts to:
  'Alpha', 'Charlie', 'aardvark', 'comma'
with this change it will instead become:
  'aardvark', 'Alpha', 'Charlie', 'comma'

If something like RFC 7613 gets broader support then there are a few
more differences for a list like:
  'éclair', 'ecstatic, 'aardvark', 'zed', 'Gamma'
currently sorts to:
  'Gamma', 'aardvark', 'ecstatic', 'zed', 'éclair'
[message trimmed]

[PATCH gamja] sort member-list with localeCompare 4 months ago

From Nolan Prescott to ~emersion/public-inbox

The difference in case sensitivity is the most obvious change with
servers like soju that support CASEMAPPING ascii and
rfc1459. Currently the list:
  'Alpha', 'aardvark', 'Charlie', 'comma'
currently sorts to:
  'Alpha', 'Charlie', 'aardvark', 'comma'
with this change it will instead become:
  'aardvark', 'Alpha', 'Charlie', 'comma'

If something like RFC 7613 gets broader support then there are a few
more differences for a list like:
  'éclair', 'ecstatic, 'aardvark', 'zed', 'Gamma'
currently sorts to:
  'Gamma', 'aardvark', 'ecstatic', 'zed', 'éclair'
[message trimmed]

[PATCH hare v2] regex: trailing hyphen not a range 7 months ago

From Nolan Prescott to ~sircmpwn/hare-dev

Per the POSIX ERE specification[0]:

> The <hyphen-minus> character shall be treated as itself if it occurs
first (after an initial '^', if any) or last in the list, or as an
ending range point in a range expression.

0: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_05

Implements: https://todo.sr.ht/~sircmpwn/hare/624
Signed-off-by: Nolan Prescott <mail@nprescott.com>
---
 regex/+test.ha | 8 ++++++++
 regex/regex.ha | 3 ++-
 2 files changed, 10 insertions(+), 1 deletion(-)
[message trimmed]

[PATCH] regex: trailing hyphen not a range 7 months ago

From Nolan Prescott to ~sircmpwn/hare-dev

Per the POSIX ERE specification[0]:

> The <hyphen-minus> character shall be treated as itself if it occurs
first (after an initial '^', if any) or last in the list, or as an
ending range point in a range expression.

0: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_05

Implements: https://todo.sr.ht/~sircmpwn/hare/624
Signed-off-by: Nolan Prescott <mail@nprescott.com>
---
 regex/+test.ha | 8 ++++++++
 regex/regex.ha | 3 ++-
 2 files changed, 10 insertions(+), 1 deletion(-)
[message trimmed]

[PATCH hare] regex: require quantifier minimum in range 7 months ago

From Nolan Prescott to ~sircmpwn/hare-dev

Intended to address https://todo.sr.ht/~sircmpwn/hare/633 where
valgrind flags a conditional jump on uninitialized value(s) stemming
from regex.parse_repetition. The source of the uninitialized value
isn't called out in the ticket but is visible with:

  valgrind --track-origins=yes .bin/hare-tests regex::find

The POSIX ERE grammar[0] does not specify a quantifier syntax with
undefined minimums (e.g. `{,2}`), this patch will error in such a case
rather than use the void value with `rep_parts.0`

0: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_05_03
Signed-off-by: Nolan Prescott <mail@nprescott.com>
---
[message trimmed]

[PATCH sr.ht-docs] correct hg email flag 1 year, 2 months ago

From Nolan Prescott to ~sircmpwn/sr.ht-dev

the correct flag is `--flag` instead of the plural `--flags`

diff --git a/hg.sr.ht/email.md b/hg.sr.ht/email.md
--- a/hg.sr.ht/email.md
+++ b/hg.sr.ht/email.md
@@ -182,10 +182,10 @@ Some projects have several repositories 
list, and it's often helpful to specify the particular repository your patch
pertains to.

If you're just doing this once, add `--flags` to `hg email`. You can specify it
multiple times if you also need to specify `--flags V2`. For instance:
If you're just doing this once, add `--flag` to `hg email`. You can specify it
multiple times if you also need to specify `--flag V2`. For instance:

[message trimmed]

[PATCH sr.ht-docs] standardize directory name 1 year, 2 months ago

From Nolan Prescott to ~sircmpwn/sr.ht-dev

the nginx configuration within sr.ht-nginx uses /var/lib/mercurial (as
does the configuration example within this document)

intended to address:
    https://todo.sr.ht/~sircmpwn/hg.sr.ht/43

diff --git a/hg.sr.ht/configuration.md b/hg.sr.ht/configuration.md
--- a/hg.sr.ht/configuration.md
+++ b/hg.sr.ht/configuration.md
@@ -20,8 +20,8 @@ This document covers the configuration p
</div>

As a repository hosting service, hg.sr.ht requires a place for storing
repositories (we recommend `/var/lib/hg/`). It also requires a `hg` user who
[message trimmed]

[PATCH hg.sr.ht] standardize directory name 1 year, 2 months ago

From Nolan Prescott to ~sircmpwn/sr.ht-dev

basically a documentation fix - the nginx configuration within
sr.ht-nginx uses /var/lib/mercurial and the hg.sr.ht alpine package
creates the same

intended to address:
    https://todo.sr.ht/~sircmpwn/hg.sr.ht/43

diff --git a/config.example.ini b/config.example.ini
--- a/config.example.ini
+++ b/config.example.ini
@@ -98,7 +98,7 @@ oauth-client-id=CHANGEME
oauth-client-secret=CHANGEME
#
# Path to mercurial repositories on disk
[message trimmed]

Re: Suspected Bug in man.sr.ht's Markdown Parser 1 year, 4 months ago

From Nolan Prescott to ~sircmpwn/sr.ht-discuss

> ... you can see that the first line ... is not like the others (2
> bullet-points directly after another) while the content of the first
> bullet-point is moved above the ToC.

You will need to add a newline after your YAML front matter to correct
the inclusion of your title in the table of contents:

```
---
title: Environment
---

# Environment variables
```