From Joseph Turner to ~pkal/public-inbox
Philip Kaludercic <philipk@posteo.net> writes: > Joseph Turner <joseph@breatheoutbreathe.in> writes: > >> I am attempting to test the issue #43 in Compat: >> >> https://github.com/emacs-compat/compat/pull/43#issuecomment-2132791230 >> >> I cloned the guix-emacs-historical repo, and then I ran >> >> guix shell -L . emacs-no-x@27.1 -- emacs -q >> >> The build fails with exit code 1. Please see the attached error log. >>
From Joseph Turner to ~pkal/public-inbox
I am attempting to test the issue #43 in Compat: https://github.com/emacs-compat/compat/pull/43#issuecomment-2132791230 I cloned the guix-emacs-historical repo, and then I ran guix shell -L . emacs-no-x@27.1 -- emacs -q The build fails with exit code 1. Please see the attached error log. Attempting to build Emacs 27.2 fails with a similar log, also attached.
From Joseph Turner to ~sircmpwn/sr.ht-discuss
Woops - I sent the wrong link to the git ref page. Here it is: https://git.sr.ht/~ushin/hyper-gateway-ushin/refs/v3.7.2
From Joseph Turner to ~sircmpwn/sr.ht-discuss
Hello! I'm running into what I believe to be the same bug while attempting to use hut to upload three build artifacts (~50M each) to the ~ushin/hyper-gateway-ushin repo. Here's an example of the failure: https://builds.sr.ht/~ushin/job/1223455#task-upload-artifacts As you can see, the following line... hut git artifact upload dist/hyper-gateway-ushin-linux --rev v3.7.2
From Joseph Turner to ~sircmpwn/sr.ht-discuss
Hi Conrad, Conrad Hoffmann <ch@bitfehler.net> writes: > Hey, > > On 5/1/24 2:08 AM, Joseph Turner wrote: >> Currently, the sourcehut renders the <head> of HTML READMEs in addition >> to the body. > > The README is supposed to be an HTML *snippet*, not an HTML document. > > See https://man.sr.ht/git.sr.ht/#setting-a-custom-readme and also the > example linked there,
From Joseph Turner to ~sircmpwn/sr.ht-discuss
I accidentally posted this report to the wrong mailing list (~sircmpwn/public-inbox). Here it is again: Currently, the sourcehut renders the <head> of HTML READMEs in addition to the body. Please see this test repository... https://git.sr.ht/~breatheoutbreathein/sourcehut-html-readme ...where the <head> content, consisting of <title> and <style> elements, is erroneously rendered above the first <h1>. Thanks for all your work on SourceHut!!
From Joseph Turner to ~sircmpwn/public-inbox
Currently, the sourcehut renders the <head> of HTML READMEs in addition to the body. Please see this test repository... https://git.sr.ht/~breatheoutbreathein/sourcehut-html-readme ...where the <head> content, consisting of <title> and <style> elements, is erroneously rendered above the first <h1>. Thanks for all your work on SourceHut!! Joseph
From to ~pkal/public-inbox
January 19, 2024 at 7:30 AM, "Philip Kaludercic" <philipk@posteo.net> wrote: > > Joseph Turner <joseph@breatheoutbreathe.in> writes: > > > > > Hi Philip! > > > > Hi, > > >
From Joseph Turner to ~pkal/public-inbox
Hi Philip! Does this make sense? Thanks! Joseph
From Joseph Turner to ~geb/numen
"John Gebbie" <me@johngebbie.com> writes: > Hi Joseph! I'm glad numen's help. > > It's really not clear, but unfortunately the "Updating recognizer > vocabulary in runtime" section/demo is just a about limiting the > vocabulary that's already there, like how numen limits the vocabulary > to the phrases for accuracy. > > You could technically use numen with a different model, but I don't > know how you can add words to the small models. > > This Vosk pull request would maybe make it possible and without model