From: "Thomas S. Dye" <email@example.com> To: Timothy <firstname.lastname@example.org> Cc: Bastien Guerry <email@example.com>, firstname.lastname@example.org Subject: Re: Dodgy Worg publishing? Date: Mon, 22 Nov 2021 07:28:28 -1000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Aloha all, Timothy <email@example.com> writes: > Hi Bastien, > >> You can check the output of Worg publishing process here: >> >> <https://builds.sr.ht/~bzg/worg> > > Ah cool, thanks for pointing that out. > >> The latest build contains a line showing that >> library-of-babel.org >> does not export: >> >> <https://builds.sr.ht/~bzg/job/627192#task-install-784> >> >> “Reference `fibs’ not found in this buffer” >> >> Can someone have a look at this and fix the ref? > > I’ve just pushed b837a85 which just defines fibs using the > content of the > example block. This may not be the best fix long-term, but > should make it work. > > All the best, > Timothy Thanks for looking into this and identifying a problem. I checked this morning and I still get a 404 error when I follow the Worg link in section 16.12 of the Org mode manual at orgmode.org. Also, is there a reason to keep worg/org-contrib/babel/library-of-babel.org in addition to worg/library-of-babel.org? All the best, Tom -- Thomas S. Dye https://tsdye.online/tsdye
next prev parent reply other threads:[~2021-11-22 17:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-24 17:20 [patch] Fix link to Library of Babel Thomas S. Dye 2021-11-21 7:04 ` Dodgy Worg publishing? (was: [patch] Fix link to Library of Babel) Timothy 2021-11-22 5:11 ` Dodgy Worg publishing? Bastien Guerry 2021-11-22 5:46 ` Timothy 2021-11-22 17:28 ` Thomas S. Dye [this message] 2021-11-22 18:10 ` Worg's library-of-babel.org (was: Dodgy Worg publishing?) Timothy 2021-11-22 18:49 ` Thomas S. Dye 2021-12-06 4:47 ` Thomas S. Dye
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Dodgy Worg publishing?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).