On 15/07/2024 12:32, Sachi King wrote:
> The nixos/unstable builds look to have been failing for a bit.  I've
> sent a patch to fix that and it should update with the next daily run.

Thanks Sachi, much appreciated.

Ian

Hmm, I think this may have been my mistake. By adding the following to 
my manifest, the shell.nix I use that pulls from <nixpkgs> now installs 
the latest version of wails etc.

repositories:
   nixpkgs: https://nixos.org/channels/nixpkgs-unstable

This is a little surprising, I would expect the nixpkgs channel for a 
NixOS unstable install to pull from nixpkgs-unstable automatically, in 
the same manner as the nixos channel, but explicitly specifying this is 
not an issue.

Thanks,

Hi,

In my latest build that uses the NixOS unstable image, it somehow pulled 
in wails 2.8.0, even though wails 2.9.1 has been available for a couple 
of weeks.

https://builds.sr.ht/~ianmjones/job/1275704#bottom

https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=wails

Does the builds infrastructure cache nixpkgs channels and need a poke, 
or should I routinely add a `nix-channel --update` to my builds 
(assuming that might work)?

> I’m new to build.yml files and a bit confused on how to do it. If I 
> understand correctly, this means that everytime I push, the whole blog, 
> including 20years of assets, is gzipped and sent to the host. Isn’t that 
> a bit overkill? Should I care? I not too far from the 1Go limitation but 
> I’m confident that I could optimize some old pictures to reduce the size 
> of the whole blog (which is not far from the 1million words mark).

You might struggle, maybe due to the tar.gz file size, but also because 
of the time taken to uncompress so many files. It's hard to tell unless 
you give it a go.

> ## Both gemini and web?
> 
> The same git repository (which I also host on sr.ht) should serve for 

And just to put a bow on it, a re-test of the private repo with private
tracker with both now referenced in a private project worked too.

Ian

Oops, no, this repo and traker didn't have a project (it does now). 🤦

I just did another test with the repo that I previously used and that
already has a project, and it worked, thanks!

Cheers,

Ian

Hey Adnan,

I just gave it a go, pushing to a `develop` branch on a private repo, it
didn't close the referenced ticket in the private tracker.

Just in case the feature only works for the default branch, I then
merged `develop` into `master` locally and pushed to sr.ht. This too did
not result in the ticket getting closed. 🤷

Am I doing something wrong?

Cheers,

Ian

Hmm, I think maybe we're at the point of needing to create a ticket?

Do you agree Drew?

If so, which tracker, git.sr.ht, todo.sr.ht, or somewhere else?

Thanks,

Ian

I tried this feature for the first time today, and it did not work for me either.

Both the git repo and tracker are in my account.

My commit[1] message was as follows, finishing with an "Implements: ..." line:

~~~
Complete Add Snippet screen.

This includes validating a new abbreviation before allowing it to be added.

Implements: https://todo.sr.ht/~ianmjones/snippetpixie/14
~~~

On Wed, 2021-10-06 at 08:19 +0200, Drew DeVault wrote:
> On Tue Oct 5, 2021 at 10:10 PM CEST, Sebastian wrote:
> > There is one detail to work out though:
> > in Markdown, inline literal text can be surrounded by any number of
> > backticks. So `this` is valid, and so is ``this``. The latter
> > allows for
> > a single backtick to be embedded inside the literal text;
> > ``something like ` this``. Is such a feature worth implementing in
> > scdoc? One part of me wants to say no, to simplify the
> > implementation.
> > But this is the only way I can think of to allow literal backticks
> > inside the text, so it may be necessary if that is desirable.
> 
> I have no strong opinions, either we could use `...` and prohibit