emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.online>
To: Timothy <tecosaur@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Worg's library-of-babel.org (was: Dodgy Worg publishing?)
Date: Sun, 05 Dec 2021 18:47:56 -1000	[thread overview]
Message-ID: <87czma49vn.fsf@tsdye.online> (raw)
In-Reply-To: <87sfvo5ad3.fsf@gmail.com>

Aloha all,

Timothy <tecosaur@gmail.com> writes:

> "Thomas S. Dye" <tsd@tsdye.online> writes:
>
>> 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.
>
> (sigh) I already fixed a 2nd issue, it looks like there's at 
> least a
> 3rd...

I still get the 404 error.

After some thought, it occurs to me that it is likely a bad idea 
to make changes to library-of-babel.org, which just contains 
source code blocks that might prove useful to Babel users.

Perhaps there is some way to indicate that this file just needs to 
be copied "as is" when Worg is published?  Or, if not, then 
perhaps the patch with the ungainly, working URL might be applied 
to the manual?

All the best,
Tom

-- 
Thomas S. Dye
https://tsdye.online/tsdye


      parent reply	other threads:[~2021-12-06  4:48 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
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 [this message]

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 \
    --in-reply-to=87czma49vn.fsf@tsdye.online \
    --to=tsd@tsdye.online \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \
    /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
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

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