---
 docs/mdtohtml.1.scd | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/mdtohtml.1.scd b/docs/mdtohtml.1.scd
index 4895c13..1727786 100644
--- a/docs/mdtohtml.1.scd
+++ b/docs/mdtohtml.1.scd
@@ -12,6 +12,8 @@ mdtohtml - convert Markdown to HTML
 The mdtohtml utility reads CommonMark-compliant Markdown from the standard input
 and writes HTML to the standard output.
 
+mdtohtml supports extensions for footnotes and syntax highlighting.
+
[message trimmed]

On Wed Mar 1, 2023 at 1:52 PM EST, Bor Grošelj Simić wrote:
> I'd expect os::status::FAILURE to match EXIT_FAILURE as defined on that
> specific platform. I'd also expect fmt::fatal to produce the same exit code
> as os::exit(os::status::FAILURE).

This is reasonable.

> So while I agree that hardcoding that to 1 like it was isn't the best
> solution, I'm in favor of introducing rt::EXIT_FAILURE or something and
> making it the same as EXIT_FAILURE from stdlib.h (which happens to be 1 on
> both currently supported platforms).

Why define it in rt instead of in os directly?

See [0].

[0]: https://lists.sr.ht/~sircmpwn/hare-dev/patches/32196

Signed-off-by: Sebastian LaVine <mail@smlavine.com>
---
 os/+freebsd/exit.ha | 2 +-
 os/+linux/exit.ha   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/os/+freebsd/exit.ha b/os/+freebsd/exit.ha
index 4b72ce4e..1b9d9b20 100644
--- a/os/+freebsd/exit.ha
+++ b/os/+freebsd/exit.ha
[message trimmed]

On Sun Feb 26, 2023 at 5:29 AM EST,  wrote:
> Next to any introduction or tutorial or the like, you need a reference 
> to the language and the standard library; that is, you need the C part 
> of <https://en.cppreference.com/>.  (It’s for C++ as well, you’ll have 
> to ignore those pages.)  That is the place to look something up you 
> don’t understand and that is the place to learn new things you don’t yet 
> know.
>
> When cppreference.com becomes too imprecise for you, you can look at the 
> standard itself.  Find links to the drafts on 
> <https://en.cppreference.com/w/c/links>.

For C, the man pages are just as useful, and don't require a web
browser.. The Linux man pages describe the functions helpfully, including

Kernighan and Ritchie's "The C Programming Language, 2nd ed." was a very helpful learning resource with me, including the examples and experiment problems. Some of it, like certain function syntaxes, are a bit outdated, and it doesn't contain some modern constructs. But I still recommend as one piece among many.
-- 
Sebastian LaVine | https://smlavine.com

On Tue Feb 21, 2023 at 2:40 PM EST, Ben Buhse wrote:
> ---
>  index.html | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/index.html b/index.html
> index be50687..c00308b 100644
> --- a/index.html
> +++ b/index.html
> @@ -263,6 +263,9 @@
>                      href="https://lists.sr.ht/~sircmpwn/email-test-drive"
>                    >mailing list archives</a> momentarily!
>                  </div>
> +                <div style="margin 0.5rem 0">

On Tue Feb 21, 2023 at 8:32 AM EST, jgart wrote:
> hi,
>
> v3 simplies some logic in the if statement
>
> ---
> (snip)
> diff --git a/yes.ha b/yes.ha
> new file mode 100644
> index 0000000..957bbc0
> --- /dev/null
> +++ b/yes.ha
> @@ -0,0 +1,22 @@
> +use fmt;

On Wed Feb 1, 2023 at 7:53 PM EST, Vlad-Stefan Harbuz wrote:
> +	for (let x = 0z; x < b.width; x += 1)
> +	for (let y = 0z; y < b.height; y += 1) {
> +		let pixel = buffer_readpixel(b, x, y);
> +		pixel = (pixel & 0xff000000) | (~(pixel & 0x00ffffff) & 0xffffff);
> +		buffer_writepixel(b, x, y, pixel);
> +	};
> +};

Interesting style for two-dimensional for-loops, I've not seen that done
before. Not sure if I like it or not, lol.

Hi Autumn,

Thanks for writing Haredo, it looks very interesting. Are you planning
to release a tagged version sometime soon? I would like to package
haredo for the AUR and that would be helpful. If not that's fine, I'll
package a git version instead.

Thanks,
Sebastian

On Sat Jan 28, 2023 at 6:09 PM EST, Bor Grošelj Simić wrote:
> > sort already contains icmp for tests, so these functions just provide a
> > public interface to use this, so code doesn't have to be duplicated.
> >
> > Closes: https://todo.sr.ht/~sircmpwn/hare/780
>
> I think actually exporting the one comparison function is a better
> approach than exporting 3 less general functions.
>
> And ints are no more special or important than any other integral type so if we
> export one such function, we might as well export such functions for all
> integral types.

Why not export one function (say searchnums) for types::numeric?