emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Library of babel help
Date: Thu, 16 Jun 2022 19:30:55 +1000	[thread overview]
Message-ID: <87letxc5nn.fsf@gmail.com> (raw)
In-Reply-To: <87pmj9c7l0.fsf@gmail.com>

Tim Cross <theophilusx@gmail.com> writes:

> Hi All,
> in my attempt to fix up some issues on the Worg site, I'm finding there
> is considerably more things broken than I initially realised. One of
> these things is 'the library of babel". 
> There is a link to the library-of-babel.org file on worg from within the
> Emacs manual. This link is currently failing with a 404 error. However,
> if you use the link embedded in the actual worg pages, you will get a
> link to the library-of-babel.org file hosted in the git repository on
> sourcehut, not worg. (it would appear that either the current build
> process is not copying the *.org files to the web server or the web
> server has not been configured to allow access to *.org files and always
> redirects you to the *.html version).  
> I believe the reason the link to the HTML file is failing is because the
> conversion from *.org to *.html is failing because of invalid emacs lisp
> in the org file source blocks. The problem is there are 5 references to
> flet, which was deprecated in Emacs 24.3. 
> To my questions -
> 1. Has anyone got a more recent version of the library-of-babel.org file
> which has the fet references replaced with something more appropriate
> (perhaps cl-flet, cl-letf or noflet)?
> If nobody has, then I can have a go at fixing it up, but as I don't use
> it, I will have trouble making sure it works correctly. 
> 2. I seem to recall that at one point, you could view the *.org sources
> of pages on worg. I think this was a useful feature and we should
> re-enable it. However, I suspect the nginx server will need some
> tweaking. Is updating the server config to allow *.org access a
> reasonable thing to do?
> 3. What should we do about the manual? We could (temporarily at least)
> change the reference to point to the current (broken) version in the
> sourcehut git repository or we can leave it until the file is again
> being served by the worg server or .....

Something else I forgot to mention just in case someone is looking at
the git repository. 

There are actually two library-of-babel.org files. One is in the root
folder and the other is in org-contrib/babel. The file
org-contrib/index.org actually links to the version in the root folder
and not the one in the same folder as it is located. Looking at them
both, I think the one in org-contrib/babel is older (certainly smaller
wiht fewer code blocks). Ironically, it doesn't have the flet issue. 

I plan to move the org-contrib/babel/library-of-babel.org file to the
archive directory to avoid confusion in future. 

  reply	other threads:[~2022-06-16  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  8:15 Library of babel help Tim Cross
2022-06-16  9:30 ` Tim Cross [this message]
2022-06-30  7:23 ` Ihor Radchenko
2022-06-30  9:06   ` Tim Cross
2022-06-30 13:25     ` Ihor Radchenko
2022-06-30 15:45     ` Serving .org files for worg (was: Re: Library of babel help) Max Nikulin
2022-06-30 17:04       ` Max Nikulin
2022-06-30 21:48       ` Tim Cross
2022-07-01  5:42         ` Max Nikulin
2022-07-29 13:10         ` Max Nikulin
2022-07-30  3:29           ` Tim Cross
2022-09-28  5:59           ` Serving .org files for worg Bastien

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87letxc5nn.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).