From: Nick Dokos <nicholas.dokos@hp.com>
To: Izzie <ml_orgmode.kapush@antichef.net>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: orgmode manual improvement suggestion.
Date: Mon, 04 Apr 2011 18:47:13 -0400 [thread overview]
Message-ID: <3857.1301957233@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Izzie <ml_orgmode.kapush@antichef.net> of "Mon, 04 Apr 2011 21:58:44 -0000." <loom.20110404T233307-302@post.gmane.org>
[forgot to cc: the list]
Izzie <ml_orgmode.kapush@antichef.net> wrote:
> Reading the manual, I found myself needing a single page version which
> I found after a quick search, I noticed that org mode manual is
> offered in several formats but not as much as emacs'[1]., which made
> me wonder if there is a org manual plain text version that can be
> downloaded somewhere.
>
If you download an org distribution (through git or a tar file or what
have you), you should be able to find the doc/org.texi file which is
used to generate the manual.
The following page
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Output-Formats.html#Output-Formats
describes briefly how to produce each output format from the texi file.
> I also want to report noticed a broken link, the first link in this
> section [2] to "this directory" leads to a 404.
>
Somebody reported that a few days ago: I guess it has not been fixed
yet.
> And that the single page version of "the compact Org-mode Guide" is
> missing.
>
Follow the link called "Generating HTML" in the above page to find
out how to generate HTML output in a single page (the input file
is doc/orgguide.texi).
But I don't know whether the single page document ever was (or should
be) available from the orgmode site, so I'm not sure I'd characterize is
as "missing": Matt and/or Jason would know better.
Nick
next prev parent reply other threads:[~2011-04-04 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 21:58 orgmode manual improvement suggestion Izzie
2011-04-04 22:47 ` Nick Dokos [this message]
2011-04-05 8:42 ` Izzie
2011-04-05 16:35 ` Nick Dokos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3857.1301957233@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=ml_orgmode.kapush@antichef.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.