emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Gerhard <gsqual@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Example text and source code in agenda - orgmanual.org typo
Date: Tue, 08 Apr 2014 08:50:51 -1000	[thread overview]
Message-ID: <m2ioqjwt84.fsf@tsdye.com> (raw)
In-Reply-To: <534428AD.6000108@gmail.com> (Gerhard's message of "Tue, 08 Apr 2014 18:49:49 +0200")

Aloha Gerhard,

Gerhard <gsqual@gmail.com> writes:

> It seems to be not completely finished, but I like 
> it.

Jonathan Leech-Pepin's texinfo exporter is really nice to work with.  At
the time I was working on orgmanual.org I thought the texinfo and pdf
output were superior to org.texi, but that was a personal preference and
is not meant to be a criticism of org.texi.

I ran out of steam on the project when Org mode moved to version 8.
There were very many changes to the manual at that time and it proved
difficult to keep up with the changes.  It might be possible to automate
the update process, but this is beyond the ability of someone with my
limited skills.  The manual process is a lot of error-prone work.

When I was working on the project I hoped the Org mode developers would
choose to "eat their own dog food" (as Carsten put it to me) and prepare
the texinfo and other documentation with Org mode source.  Of course,
that hope was based on considerable naivete and an imperfect
understanding of how Org mode is connected with the rest of the Emacs
world.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2014-04-08 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 16:49 Example text and source code in agenda - orgmanual.org typo Gerhard
2014-04-08 18:50 ` Thomas S. Dye [this message]
2014-04-08 19:31   ` Nicolas Goaziou
2014-04-09  7:40     ` Gerhard

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=m2ioqjwt84.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gsqual@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).