emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: emacs-orgmode emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: broken link in manual
Date: Thu, 16 Jul 2009 17:44:29 -0400	[thread overview]
Message-ID: <13666.1247780669@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bastien <bastienguerry@googlemail.com> of "Thu, 16 Jul 2009 21:43:27 +0200." <871vog9zxc.fsf@bzg.ath.cx>

Bastien <bastienguerry@googlemail.com> wrote:

> Greg Newman <greg@20seven.org> writes:
> > I found a broken link in the manual just now.  The appendix link A
> > extensions (on the left nav) gives a 404.
> I can't find the broken link.  
> Btw, the manual lives in two locations:
> http://orgmode.org/org.html
> http://orgmode.org/manual/
> Can you send the relevant link?

The navigation menu on the left of the page is out of sync: it contains
a link to a non-existent appendix "A Extensions" in between the
"Miscellaneous" link and the "B Hacking" link. The manual itself goes
from Ch. 14 "Miscellaneous" to "Hacking" as its Next: link.  The bad
link is



PS. Here is a fragment of the page source:

<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<li><a name="toc_Top" href="index.html#Top">Org Mode Manual</a>
<li><a name="toc_Introduction" href="Introduction.html#Introduction">1 Introduction</a>
<li><a name="toc_Document-Structure" href="Document-Structure.html#Document-Structure">2 Document Structure</a>

<li><a name="toc_Tables" href="Tables.html#Tables">3 Tables</a>
<li><a name="toc_Hyperlinks" href="Hyperlinks.html#Hyperlinks">4 Hyperlinks</a>
<li><a name="toc_TODO-Items" href="TODO-Items.html#TODO-Items">5 TODO Items</a>
<li><a name="toc_Tags" href="Tags.html#Tags">6 Tags</a>
<li><a name="toc_Properties-and-Columns" href="Properties-and-Columns.html#Properties-and-Columns">7 Properties and Columns</a>
<li><a name="toc_Dates-and-Times" href="Dates-and-Times.html#Dates-and-Times">8 Dates and Times</a>
<li><a name="toc_Capture" href="Capture.html#Capture">9 Capture</a>
<li><a name="toc_Agenda-Views" href="Agenda-Views.html#Agenda-Views">10 Agenda Views</a>
<li><a name="toc_Embedded-LaTeX" href="Embedded-LaTeX.html#Embedded-LaTeX">11 Embedded LaTeX</a>

<li><a name="toc_Exporting" href="Exporting.html#Exporting">12 Exporting</a>
<li><a name="toc_Publishing" href="Publishing.html#Publishing">13 Publishing</a>
<li><a name="toc_Miscellaneous" href="Miscellaneous.html#Miscellaneous">14 Miscellaneous</a>
<li><a name="toc_Extensions" href="Extensions.html#Extensions">A Extensions</a>                <========================THIS ONE
<li><a name="toc_Hacking" href="Hacking.html#Hacking">B Hacking</a>
<li><a name="toc_History-and-Acknowledgments" href="History-and-Acknowledgments.html#History-and-Acknowledgments">C History and Acknowledgments</a>
<li><a name="toc_Main-Index" href="Main-Index.html#Main-Index">Main Index</a>
<li><a name="toc_Key-Index" href="Key-Index.html#Key-Index">Key Index</a>


  reply	other threads:[~2009-07-16 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 10:09 broken link in manual Greg Newman
2009-07-16 19:43 ` Bastien
2009-07-16 21:44   ` Nick Dokos [this message]
2009-07-16 21:51     ` Greg Newman
2009-07-16 22:00     ` Bastien
2009-07-16 22:05       ` Greg Newman
2009-08-03  4:30       ` Carsten Dominik

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=13666.1247780669@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bastienguerry@googlemail.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).