emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Newman <greg@20seven.org>
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 18:05:30 -0400	[thread overview]
Message-ID: <71454fac0907161505u52c80e12sb37017c6d6a5af9b@mail.gmail.com> (raw)
In-Reply-To: <87ocrkl24f.fsf@bzg.ath.cx>

[-- Attachment #1.1: Type: text/plain, Size: 793 bytes --]

you rock Basetien!

On Thu, Jul 16, 2009 at 6:00 PM, Bastien <bastienguerry@googlemail.com>wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> > 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
> >
> >    http://orgmode.org/manual/Extensions.html#Extensions
> Thanks.
> I've fixed this by updating the manual in http://orgmode.org/manual/
> This manual don't have the fancy navigation, but since it's available
> from http://orgmode.org/org.html I guess it's all right.  At least the
> link is not broken anymore.
> --
>  Bastien

[-- Attachment #1.2: Type: text/html, Size: 1487 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

  reply	other threads:[~2009-07-16 22:05 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
2009-07-16 21:51     ` Greg Newman
2009-07-16 22:00     ` Bastien
2009-07-16 22:05       ` Greg Newman [this message]
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=71454fac0907161505u52c80e12sb37017c6d6a5af9b@mail.gmail.com \
    --to=greg@20seven.org \
    --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).