emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Ori <ori@oribarbut.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bug report: URL capitalization in online manual
Date: Mon, 10 Feb 2020 07:48:21 +0100	[thread overview]
Message-ID: <874kvzdjka.fsf@gnu.org> (raw)
In-Reply-To: <CACyCJqX3xrJsctFEmTNUp6HwzGE1M83KGnc9atYt_LUpgk69Bw@mail.gmail.com> (ori@oribarbut.com's message of "Sun, 9 Feb 2020 13:49:04 -0500")

Hi Ori,

thanks a lot for taking the trouble to produce this file, very useful.

I've now installed the rewrite rules on the server and all these links
are redirecting correctly. Given the amount of Org documentation links
living out there, that's really a good idea.

> Versioned folders living side-by-side.

I've thought about this, but I think it is too much. If someone thinks
otherwise, anyone can volunteer to maintain multiple versions of the
documentation on the website.

Thanks again!


      reply	other threads:[~2020-02-10  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08 18:51 Possible bug report: URL capitalization in online manual Ori Barbut
2020-02-08 19:15 ` Bastien
2020-02-08 19:25   ` Ori
2020-02-08 19:56     ` Bastien
2020-02-09 18:49       ` Ori
2020-02-10  6:48         ` Bastien [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:

  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=874kvzdjka.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ori@oribarbut.com \


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