emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gerhard <gsqual@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Example text and source code in agenda - orgmanual.org typo
Date: Wed, 09 Apr 2014 09:40:08 +0200	[thread overview]
Message-ID: <5344F958.3030402@gmail.com> (raw)
In-Reply-To: <87ioqjvcrk.fsf@gmail.com>

Hello,

Am 08.04.2014 21:31, schrieb Nicolas Goaziou:
> ntsd@tsdye.com (Thomas S. Dye) writes:
>
>> 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.
> FWIW, I still think it would be good to have our documentation in our
> home-made format.
>
> Of course, there's the problem of backporting documentation fixes coming
> from Emacs developers, but we might find volunteers to take care of it.
> Also, it doesn't happen very frequently.
>
> There may be other road blocks that I'm not aware of, but if there is
> none, I suggest to think about the feasibility of this project again.
>
now I know more about the history and status of this project, thanks to 
your answers. Although it looks to me as a good starting point, It also 
seems to take quite a bit of knowledge about many things to go on here, 
so I am not the one who could help. But maybe the volunteers can be found.

Regards,
Gerhard

      reply	other threads:[~2014-04-09  7:40 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
2014-04-08 19:31   ` Nicolas Goaziou
2014-04-09  7:40     ` Gerhard [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:
  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=5344F958.3030402@gmail.com \
    --to=gsqual@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=tsd@tsdye.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).