~humm

~humm/public-inbox

Last active 2 months ago
View more

Recent activity

Re: [PATCH harelang.org] blog: add regex 3 months ago

From Lennart Jablonka to ~sircmpwn/hare-dev

wow vladh your ascii diagrams are so nice

-- 
Lennart

Re: bleh 3 months ago

From Lennart Jablonka to ~sircmpwn/public-inbox

Quoth Merlin Büge:
>If you wanted to tell me I'm pedantic (or anything like that): I usually
>notify blog post authors of typos when I find them. I think for a popular blog
>like Drew's it's nice to correct them. But I usually do that in private.

Oh, no, I didn’t mean that.  Correcting tpyos for published texts is 
a good thing.

I liked your message.  I think pointing out a ytpo is a good way of 
starting a message.

-- 
Lennart

Re: bleh 3 months ago

From Lennart Jablonka to ~sircmpwn/public-inbox

Quoth Merlin Büge:
>there is a typo:

There is a tyop:

>beleive that at some point in your self-development, you get to a point

-- 
Lennart

Re: [PATCH harec] Use C99 format specifiers in fprintf for OpenBSD compatibility 3 months ago

From Lennart Jablonka to ~sircmpwn/hare-dev

Quoth Jason Lenz:
> Subject: Re: [PATCH harec] Use C99 format specifiers in fprintf for 
>  OpenBSD compatibility

For future reference, don’t put such a rationale in the summary.  If 
alignment with the standard would need a rationale at all, it should be 
put into the body of the message.

-- 
Lennart

Re: Sending images in patches 4 months ago

From Humm to ~sircmpwn/sr.ht-discuss

Quoth ch@raiguard.me:
>Where it all breaks down is the email-based patch workflow. As far as
>I can tell, you can't send updates to images in patches. Additionally,
>lists.sr.ht has a 10 MB size limit, which I found out while I was
>testing it. This makes sending images in patches impractical, even if
>it were possible.
>
>For the most part, not being able to send image patches is not a
>show-stopper. However, when someone does contribute art changes[2], they
>won't be able to do so with Sourcehut's mailing lists.
>
>Two solutions I have thought of:
>- Give the contributor write access to the repository, and have them do
>their work in a branch. They send an email when they are done, and I

Re: [PATCH hare] encoding::json: add unparse 4 months ago

From Humm to ~sircmpwn/hare-dev

>+		case let r: rune =>
>+			switch (r) {
>+			case '\b' =>
>+				z += fmt::fprint(out, `\b`)?;
>+			case '\f' =>
>+				z += fmt::fprint(out, `\f`)?;
>+			case '\n' =>
>+				z += fmt::fprint(out, `\n`)?;
>+			case '\r' =>
>+				z += fmt::fprint(out, `\r`)?;
>+			case '\t' =>
>+				z += fmt::fprint(out, `\t`)?;
>+			case '\"' =>
>+				z += fmt::fprint(out, `\"`)?;

Re: [PATCH hare] encoding::json: fix iterator next 4 months ago

From Humm to ~sircmpwn/public-inbox

>Let me know if there is a better way of fixing the issue at hand.

Which is what?  Put the problem in the commit message.

-- 
Humm

Re: [PATCH hare] fmt::fatal - exit with 255 4 months ago

From Humm to ~sircmpwn/hare-dev

Quoth the lemons:
>---
>fmt::fatal returning 255 will more reliably indicate a generic error
>condition.
>
>there are cases where the required exit status of a program is not
>binary between a generic error condition and success. in POSIX, 0 always
>indicates success; however, 1 does not always indicate a generic error.
>examples of this are:
>
>[…]
>
>255 is frequently used as an error status by convention. among POSIX
>utilities, values >127 are always specified to be a generic error except

[PATCH hare] encoding::json: refer to RFC 8259 in README 4 months ago

From Humm to ~sircmpwn/hare-dev

Also add a note about other specifications.

Signed-off-by: Humm <hummsmith42@gmail.com>
---
 encoding/json/README | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/encoding/json/README b/encoding/json/README
index 0628c718..348178fc 100644
--- a/encoding/json/README
+++ b/encoding/json/README
@@ -1,5 +1,6 @@
This module provides an implementation of the JavaScript Object Notation (JSON)
format, defined by RFC 7159. A lexer for JSON values is provided, which may be
[message trimmed]

Re: Non-systemd user services 4 months ago

From Humm to ~sircmpwn/public-inbox

Quoth Jan “Khardix” Staněk:
>I was looking around, but did not find any popular alternative to it. 
>Most of the init systems/service managers deal only with system-level 
>stuff; nothing on the user level.
>
>Is anyone aware of such a service manager they would reccomend?

s6.  s6 doesn’t care about being system- or user-level.

-- 
Humm